sched: group scheduler related patches (V4)
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest5 patches 4 repliesIn review
Changes since V3 (http://marc.info/?l=linux-kernel&m=119605252303359) from the cover letter
- Fix bug in setting SCHED_RR priority for load_balance_monitor thread
- Fix coding style related issues
- Separate "introduction of lock_doms_cur() API" into a separate patch
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | sched: code cleanupkernel/ | +3 | 0 replies | |
| 2/5 | sched: minor fixes for group schedulerkernel/ kernel/ | +29 | 0 replies | |
| 3/5 | sched: change how cpu load is calculatedkernel/ kernel/ kernel/ | +59 | 0 replies | |
| 4/5 | sched: introduce a mutex and corresponding API to serialize access to doms_cur[] arraykernel/ | +19 | 0 replies | |
| 5/5 | sched: Improve fairness of cpu bandwidth allocation for task groupsinclude/ kernel/ kernel/ +1 more | +330 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Patch 0/5] sched: group scheduler related patches (V4)
Quoted 1 line · Ingo Molnar
the first
SCHED_RRpriority is 1, not 0 - so this call will always fail.
Thanks for spotting this bug and rest of your review comments.
Here's V4 of the patchset, aimed at improving fairness of cpu bandwidth allocation for task groups.
Changes since V3 (http://marc.info/?l=linux-kernel&m=119605252303359):
- Fix bug in setting SCHED_RR priority for load_balance_monitor thread
- Fix coding style related issues
- Separate "introduction of lock_doms_cur() API" into a separate patch
I have also tested this patchset against your latest git tree as of today morning.
Please apply if there are no major concerns.
Signature · 2 lines
Regards, vatsa