aboutsummaryrefslogtreecommitdiff
path: root/arch/x86/include
diff options
context:
space:
mode:
authorPeter Zijlstra <a.p.zijlstra@chello.nl>2009-09-17 09:01:20 +0200
committerIngo Molnar <mingo@elte.hu>2009-09-17 10:40:30 +0200
commitde69a80be32445b0a71e8e3b757e584d7beb90f7 (patch)
tree3a8d6bf8e5aded3c371e5dc090b8874305952d1f /arch/x86/include
parentad4b78bbcbab66998b05d422ac6106b645796e54 (diff)
sched: Stop buddies from hogging the system
Clear buddies more agressively. The (theoretical, haven't actually observed any of this) problem is that when we do not select either buddy in pick_next_entity() because they are too far ahead of the left-most task, we do not clear the buddies. This means that as soon as we service the left-most task, these same buddies will be tried again on the next schedule. Now if the left-most task was a pure hog, it wouldn't have done any wakeups and it wouldn't have set buddies of its own. That leads to the old buddies dominating, which would lead to bad latencies. Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl> Cc: Mike Galbraith <efault@gmx.de> LKML-Reference: <new-submission> Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'arch/x86/include')
0 files changed, 0 insertions, 0 deletions