load balancing fixes
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 15 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | sched: fix and clean up calculate_imbalancekernel/ | +8 | 14 replies | |
| 2/2 | sched: make update_sd_pick_busiest return true on a busier sdkernel/ | +28 | 1 reply |
Reviews trailers per patch
1 of 2 patches has a Reviewed-by or Acked-by.
| Patch | Michael Neuling |
|---|---|
| 1/2 | |
| 2/2 | A-b A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/2] load balancing fixes
Currently update_sd_pick_busiest only identifies the busiest sd that is either overloaded, or has a group imbalance. When no sd is imbalanced or overloaded, the load balancer fails to find the busiest domain.
This breaks load balancing between domains that are not overloaded, in the !SD_ASYM_PACKING case. This patch makes update_sd_pick_busiest return true when the busiest sd yet is encountered.
Groups are ranked in the order overloaded > imbalanced > other, with higher ranked groups getting priority even when their load is lower. This is necessary due to the possibility of unequal capacities and cpumasks between domains within a sched group.
Calculate_imbalance knows how to deal with the situation where a less loaded group is picked, but will only do so when sgs->group_imb is set. This handling needs to be extended to all situations where the busiest load is below the average load.