summaryrefslogtreecommitdiffstats
path: root/drivers/staging
diff options
context:
space:
mode:
authorPaul Turner <pjt@google.com>2011-07-21 09:43:36 -0700
committerIngo Molnar <mingo@elte.hu>2011-08-14 12:03:40 +0200
commit64660c864f46202b932b911a69deb09805bdbaf8 (patch)
treecf49455195a184e4962c6cac2c39c4f690d74ddc /drivers/staging
parent8277434ef1202ce30315f8edb3fc760aa6e74493 (diff)
downloadlinux-64660c864f46202b932b911a69deb09805bdbaf8.tar.gz
linux-64660c864f46202b932b911a69deb09805bdbaf8.tar.bz2
linux-64660c864f46202b932b911a69deb09805bdbaf8.zip
sched: Prevent interactions with throttled entities
From the perspective of load-balance and shares distribution, throttled entities should be invisible. However, both of these operations work on 'active' lists and are not inherently aware of what group hierarchies may be present. In some cases this may be side-stepped (e.g. we could sideload via tg_load_down in load balance) while in others (e.g. update_shares()) it is more difficult to compute without incurring some O(n^2) costs. Instead, track hierarchicaal throttled state at time of transition. This allows us to easily identify whether an entity belongs to a throttled hierarchy and avoid incorrect interactions with it. Also, when an entity leaves a throttled hierarchy we need to advance its time averaging for shares averaging so that the elapsed throttled time is not considered as part of the cfs_rq's operation. We also use this information to prevent buddy interactions in the wakeup and yield_to() paths. Signed-off-by: Paul Turner <pjt@google.com> Reviewed-by: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com> Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl> Link: http://lkml.kernel.org/r/20110721184757.777916795@google.com Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'drivers/staging')
0 files changed, 0 insertions, 0 deletions