Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Gracefully handle hotplug in scx_rusty #218

Merged
merged 2 commits into from
Apr 4, 2024
Merged

Gracefully handle hotplug in scx_rusty #218

merged 2 commits into from
Apr 4, 2024

Commits on Apr 4, 2024

  1. uei: Export exit_code from UserExitInfo 

    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]>
    @Byte-Lab
    Byte-Lab committed Apr 4, 2024
    Configuration menu
    Copy the full SHA
    052ce42 View commit details
    Browse the repository at this point in the history

  2. rusty: Support restarting rusty on hotplug events 

    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
    Byte-Lab committed Apr 4, 2024
    Configuration menu
    Copy the full SHA
    622b61d View commit details
    Browse the repository at this point in the history