summaryrefslogtreecommitdiff
path: root/block/elevator.c
diff options
context:
space:
mode:
authorPeter Zijlstra <peterz@infradead.org>2013-07-27 01:48:42 +0400
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2013-08-20 19:43:02 +0400
commitdead45bd0527751cc9e71c0547d8f19f498441ed (patch)
treea2ca8e9e060f2df9c944a4f831e3eb4883f0dbd4 /block/elevator.c
parentf30d87b004dcb4b260dcb2667d5ef6998f4aac1f (diff)
downloadlinux-dead45bd0527751cc9e71c0547d8f19f498441ed.tar.xz
sched: Ensure update_cfs_shares() is called for parents of continuously-running tasks
commit bf0bd948d1682e3996adc093b43021ed391983e6 upstream. We typically update a task_group's shares within the dequeue/enqueue path. However, continuously running tasks sharing a CPU are not subject to these updates as they are only put/picked. Unfortunately, when we reverted f269ae046 (in 17bc14b7), we lost the augmenting periodic update that was supposed to account for this; resulting in a potential loss of fairness. To fix this, re-introduce the explicit update in update_cfs_rq_blocked_load() [called via entity_tick()]. Reported-by: Max Hailperin <max@gustavus.edu> Signed-off-by: Peter Zijlstra <peterz@infradead.org> Reviewed-by: Paul Turner <pjt@google.com> Link: http://lkml.kernel.org/n/tip-9545m3apw5d93ubyrotrj31y@git.kernel.org Signed-off-by: Ingo Molnar <mingo@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'block/elevator.c')
0 files changed, 0 insertions, 0 deletions