diff options
| author | Paul Turner | 2011-01-15 02:57:50 +0100 |
|---|---|---|
| committer | Ingo Molnar | 2011-01-18 15:09:38 +0100 |
| commit | 977dda7c9b540f48b228174346d8b31542c1e99f (patch) | |
| tree | 77d40bcc72c1590dfcaeadb60e92a270bd204c52 /kernel/trace/trace_workqueue.c | |
| parent | sched: Constify function scope static struct sched_param usage (diff) | |
| download | kernel-qcow2-linux-977dda7c9b540f48b228174346d8b31542c1e99f.tar.gz kernel-qcow2-linux-977dda7c9b540f48b228174346d8b31542c1e99f.tar.xz kernel-qcow2-linux-977dda7c9b540f48b228174346d8b31542c1e99f.zip | |
sched: Update effective_load() to use global share weights
Previously effective_load would approximate the global load weight present on
a group taking advantage of:
entity_weight = tg->shares ( lw / global_lw ), where entity_weight was provided
by tg_shares_up.
This worked (approximately) for an 'empty' (at tg level) cpu since we would
place boost load representative of what a newly woken task would receive.
However, now that load is instantaneously updated this assumption is no longer
true and the load calculation is rather incorrect in this case.
Fix this (and improve the general case) by re-writing effective_load to take
advantage of the new shares distribution code.
Signed-off-by: Paul Turner <pjt@google.com>
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
LKML-Reference: <20110115015817.069769529@google.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'kernel/trace/trace_workqueue.c')
0 files changed, 0 insertions, 0 deletions