Gracefully handle hotplug in scx_rusty #218
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Newer kernels also support exiting gracefully with an exit code. Let's update the UserExitInfo struct to also read and export this value. Signed-off-by: David Vernet <[email protected]>
The scx_rusty scheduler does not support hotplug, and expects a static host topology throughout its runtime. Though the kernel does have support for detecting hotplug events, we currently don't detect this in the kernel, nor surface it to user space when it happens. Now that we have scx_bpf_exit(), we can gracefully exit the kernel in the event of a hotplug, and communicate to user space that it should restart the scheduler. This patch adds that support to scx_rusty. Note that this assumes that we're running on a recent enough kernel that has scx_bpf_exit(). If it doesn't, then we instead just error out of the kernel scheduler and exit the application. Signed-off-by: David Vernet <[email protected]>
Byte-Lab
changed the title
htejun
approved these changes
Apr 4, 2024
|
It'd be nice if there was a generic way to apply this change automatically to all the schedulers, considering that most (all?) of them are not handling CPU hotplugging nicely at the moment, maybe a flag Anyway, this looks good to me for now, I'll do the same in scx_rustland_core. |
|
Oh yeah, that's a good idea, definitely seems like this would be something generally useful. @htejun wdyt? |
|
Yeah, it'd be nice to make this generic in scx_utils. Traits are tough to do with skels unfortunately, so we might have to do even more macros, which is a bit sad but not the end of the world. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The scx_rusty scheduler does not support hotplug, and expects a static
host topology throughout its runtime. Though the kernel does have
support for detecting hotplug events, we currently don't detect this in
the kernel, nor surface it to user space when it happens. Now that we
have scx_bpf_exit(), we can gracefully exit the kernel in the event of a
hotplug, and communicate to user space that it should restart the
scheduler.
This patch adds that support to scx_rusty. Note that this assumes that
we're running on a recent enough kernel that has scx_bpf_exit(). If it
doesn't, then we instead just error out of the kernel scheduler and exit
the application.