Message-ID: <44F3178F.8010508@linux.intel.com>
Date: Mon, 28 Aug 2006 18:19:27 +0200
From: Arjan van de Ven <arjan@linux.intel.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Andreas Mohr <andi@rhlx01.fht-esslingen.de>
CC: linux-kernel@vger.kernel.org, akpm@osdl.org, mingo@elte.hu,
       jesse.barnes@intel.com, dwalker@mvista.com
Subject: Re: [PATCH] maximum latency tracking infrastructure (version 3)
References: <1156780080.3034.207.camel@laptopd505.fenrus.org> <20060828161145.GA25161@rhlx01.fht-esslingen.de>
In-Reply-To: <20060828161145.GA25161@rhlx01.fht-esslingen.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 994
Lines: 23

Andreas Mohr wrote:
> Hi,
> 
> On Mon, Aug 28, 2006 at 05:48:00PM +0200, Arjan van de Ven wrote:
>> The proposed solution is to have an interface where drivers can
>> * announce the maximum latency (in microseconds) that they can deal with
>> * modify this latency
>> * give up their constraint
>> and a function where the code that decides on power saving strategy can query
>> the current global desired maximum.
> 
> Nifty (aka "dumb") idea: would it make sense to enable drivers to register a
> callback "we're going to go idle now" to e.g. let a driver refill or
> service its hardware buffers the very moment before idling? 

I could have sworn there was an idle call notifier already\

ah there is on x86-64 but it is architecture specific...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/