[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1351180603.12171.31.camel@twins>
Date: Thu, 25 Oct 2012 17:56:43 +0200
From: Peter Zijlstra <a.p.zijlstra@...llo.nl>
To: Preeti U Murthy <preeti@...ux.vnet.ibm.com>
Cc: svaidy@...ux.vnet.ibm.com, linux-kernel@...r.kernel.org,
mingo@...nel.org, venki@...gle.com, robin.randhawa@....com,
linaro-dev@...ts.linaro.org, mjg59@...f.ucam.org,
viresh.kumar@...aro.org, akpm@...ux-foundation.org,
amit.kucheria@...aro.org, deepthi@...ux.vnet.ibm.com,
paul.mckenney@...aro.org, arjan@...ux.intel.com,
paulmck@...ux.vnet.ibm.com, srivatsa.bhat@...ux.vnet.ibm.com,
vincent.guittot@...aro.org, tglx@...utronix.de,
Arvind.Chauhan@....com, pjt@...gle.com, Morten.Rasmussen@....com,
linux-arm-kernel@...ts.infradead.org, suresh.b.siddha@...el.com
Subject: Re: [RFC PATCH 00/13] sched: Integrating Per-entity-load-tracking
with the core scheduler
OK, so I tried reading a few patches and I'm completely failing.. maybe
its late and my brain stopped working, but it simply doesn't make any
sense.
Most changelogs and comments aren't really helping either. At best they
mention what you're doing, not why and how. This means I get to
basically duplicate your entire thought pattern and I might as well do
the patches myself.
I also don't see the 'big' picture of what you're doing, you start out
by some weird avoid short running task movement.. why is that a good
start?
I would have expected a series like this to replace rq->cpu_load /
rq->load with a saner metric and go from there.. instead it looks like
its going about at things completely backwards. Fixing small details
instead of the big things.
Do explain..
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists