-
Notifications
You must be signed in to change notification settings - Fork 39
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.
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
Fix some things in Nest #39
Merged
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
Julia pointed out that our current implementation of r_impatient is incorrect. r_impatient is meant to be a mechanism for more aggressively growing the primary nest if a task repeatedly isn't able to find a core. Right now, we trigger r_impatient if we're not able to find an attached or previous core in the primary nest, but we _should_ be triggering it only if we're unable to find _any_ core in the primary nest. Fixing the implementation to do this drastically decreases how aggressively we grow the primary nest when r_impatient is in effect. Reported-by: Julia Lawall <julia.lawall@inria.fr> Signed-off-by: David Vernet <void@manifault.com>
The core sched code calls select_task_rq() in a few places: the task wakeup path (typical path), the fork() path, and the exec() path. For nest scheduling, we don't want to select a core from the nest on the exec() path. If we were previously able to find an idle core, we would have found it on the fork() path, so we don't gain much by checking on the exec() path. In fact, it's actually harmful, because we could incorrectly blow up the primary nest unnecessarily by bumping the same task between multiple cores for no reason. Let's just opt-out of select_task_rq calls on the exec() path. Suggested-by: Julia Lawall <julia.lawall@inria.fr> Signed-off-by: David Vernet <void@manifault.com>
The only feedback I can give: built, tested, appears to have no problems.
|
htejun
approved these changes
Dec 18, 2023
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.
Julia noticed a few things that can be improved in scx_nest. Address them here