[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141030143853.GF23531@worktop.programming.kicks-ass.net>
Date: Thu, 30 Oct 2014 15:38:53 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Daniel Lezcano <daniel.lezcano@...aro.org>
Cc: linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
axboe@...nel.dk, rafael.j.wysocki@...el.com, mingo@...nel.org,
preeti@...ux.vnet.ibm.com, Morten.Rasmussen@....com,
mturquette@...aro.org, tuukka.tikkanen@...aro.org,
nicolas.pitre@...aro.org, patches@...aro.org
Subject: Re: [RFD PATCH 00/10] cpuidle: Predict the next events with the IO
latencies
On Wed, Oct 22, 2014 at 03:57:43PM +0200, Daniel Lezcano wrote:
> After discussing at the LPC2014 Dusseldorf, it appears the idea is
> good but the approach is wrong. The latency tracking must be done at
> the device level, per device and not in the task as what is doing this
> patchset.
end_page_writeback()->test_clear_page_writeback()->__bdi_writeout_inc()
Is the IO completion path that has a fair amount of statistics in, maybe
some of that is usable.
--
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