summaryrefslogtreecommitdiffstats
path: root/include/linux
diff options
context:
space:
mode:
authorPeter Williams <pwil3058@bigpond.net.au>2006-06-27 02:54:37 -0700
committerLinus Torvalds <torvalds@g5.osdl.org>2006-06-27 17:32:44 -0700
commit615052dc3bf96278a843a64d3d1eea03532028c3 (patch)
treee7d5c61bd244e5fbde4ada9ae2ef1ebe7923fb53 /include/linux
parent50ddd96917e4548b3813bfb5dd6f97f052b652bd (diff)
downloadop-kernel-dev-615052dc3bf96278a843a64d3d1eea03532028c3.zip
op-kernel-dev-615052dc3bf96278a843a64d3d1eea03532028c3.tar.gz
[PATCH] sched: Avoid unnecessarily moving highest priority task move_tasks()
Problem: To help distribute high priority tasks evenly across the available CPUs move_tasks() does not, under some circumstances, skip tasks whose load weight is bigger than the designated amount. Because the highest priority task on the busiest queue may be on the expired array it may be moved as a result of this mechanism. Apart from not being the most desirable way to redistribute the high priority tasks (we'd rather move the second highest priority task), there is a risk that this could set up a loop with this task bouncing backwards and forwards between the two queues. (This latter possibility can be demonstrated by running a nice==-20 CPU bound task on an otherwise quiet 2 CPU system.) Solution: Modify the mechanism so that it does not override skip for the highest priority task on the CPU. Of course, if there are more than one tasks at the highest priority then it will allow the override for one of them as this is a desirable redistribution of high priority tasks. Signed-off-by: Peter Williams <pwil3058@bigpond.com.au> Cc: Ingo Molnar <mingo@elte.hu> Cc: "Siddha, Suresh B" <suresh.b.siddha@intel.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud