diff options
author | Peter Zijlstra <a.p.zijlstra@chello.nl> | 2012-05-11 00:22:12 +0200 |
---|---|---|
committer | Ingo Molnar <mingo@kernel.org> | 2012-05-14 15:05:28 +0200 |
commit | e44bc5c5d00ee9b56dd87db47ed827d52948b9fa (patch) | |
tree | e0e5c30591d8bae335a101458f311e5972175a69 /kernel/sched/debug.c | |
parent | 556061b00c9f2fd6a5524b6bde823ef12f299ecf (diff) | |
download | op-kernel-dev-e44bc5c5d00ee9b56dd87db47ed827d52948b9fa.zip op-kernel-dev-e44bc5c5d00ee9b56dd87db47ed827d52948b9fa.tar.gz |
sched/fair: Improve the ->group_imb logic
Group imbalance is meant to deal with situations where affinity masks
and sched domains don't align well, such as 3 cpus from one group and
6 from another. In this case the domain based balancer will want to
put an equal amount of tasks on each side even though they don't have
equal cpus.
Currently group_imb is set whenever two cpus of a group have a weight
difference of at least one avg task and the heaviest cpu has at least
two tasks. A group with imbalance set will always be picked as busiest
and a balance pass will be forced.
The problem is that even if there are no affinity masks this stuff can
trigger and cause weird balancing decisions, eg. the observed
behaviour was that of 6 cpus, 5 had 2 and 1 had 3 tasks, due to the
difference of 1 avg load (they all had the same weight) and nr_running
being >1 the group_imbalance logic triggered and did the weird thing
of pulling more load instead of trying to move the 1 excess task to
the other domain of 6 cpus that had 5 cpu with 2 tasks and 1 cpu with
1 task.
Curb the group_imbalance stuff by making the nr_running condition
weaker by also tracking the min_nr_running and using the difference in
nr_running over the set instead of the absolute max nr_running.
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Link: http://lkml.kernel.org/n/tip-9s7dedozxo8kjsb9kqlrukkf@git.kernel.org
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'kernel/sched/debug.c')
0 files changed, 0 insertions, 0 deletions