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.

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

scx_bpfland: minor cleanups #871

Merged
merged 4 commits into from
Nov 2, 2024
Merged

scx_bpfland: minor cleanups #871

merged 4 commits into from
Nov 2, 2024

Conversation

arighi
Copy link
Contributor

@arighi arighi commented Oct 31, 2024

Nothing significant, just minor cleanups / restyling and a small fix to restore the old max nvcsw limit that was incorrectly changed during the lowlatency mode refactoring.

Evalute the amount of voluntary context switches directly in the BPF
code, without relying on the kernel p->nvcsw metric.

Signed-off-by: Andrea Righi <[email protected]>
Get rid of the static MAX_LATENCY_WEIGHT and always rely on the value
specified by --nvcsw-max-thresh.

This allows to tune the maximum latency weight when running in
lowlatency mode (via --nvcsw-max-thresh) and it also restores the
maximum nvcsw limit in non-lowlatency mode, that was incorrectly changed
during the lowlatency refactoring.

Fixes: 4d68133 ("scx_bpfland: rework lowlatency mode to adjust tasks priority")
Signed-off-by: Andrea Righi <[email protected]>
The dynamic nvcsw threshold is not used anymore in the scheduler and it
doesn't make sense to report it in the scheduler's statistics, so let's
just drop it.

Signed-off-by: Andrea Righi <[email protected]>
@arighi arighi enabled auto-merge October 31, 2024 22:19
@arighi arighi disabled auto-merge November 2, 2024 15:19
@arighi arighi merged commit 20c0372 into main Nov 2, 2024
40 of 42 checks passed
@arighi arighi deleted the bpfland-minor-cleanups branch November 2, 2024 15:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants