Messages in this thread | | | Date | Tue, 07 May 2013 14:17:46 +0800 | From | Alex Shi <> | Subject | Re: [PATCH v5 5/7] sched: compute runnable load avg in cpu_load and cpu_avg_load_per_task |
| |
On 05/06/2013 07:10 PM, Peter Zijlstra wrote: >> > The runnable_avgs themselves actually have a fair bit of history in >> > them already (50% is last 32ms); but given that they don't need to be >> > cut-off to respond to load being migrated I'm guessing we could >> > actually potentially get by with just "instaneous" and "use averages" >> > where appropriate? > Sure,. worth a try. If things fall over we can always look at it again. > >> > We always end up having to re-pick/tune them based on a variety of >> > workloads; if we can eliminate them I think it would be a win. > Agreed, esp. the plethora of weird idx things we currently have. If we need to > re-introduce something it would likely only be the busy case and for that we > can immediately link to the balance interval or so. > > >
I like to have try bases on this patchset. :)
First, we can remove the idx, to check if the removing is fine for our benchmarks, kbuild, dbench, tbench, hackbench, aim7, specjbb etc.
If there are some regression. we can think more.
-- Thanks Alex
| |