From: Arjan van de Ven <arjan@linux.intel.com>
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)
Date: Mon, 28 Aug 2006 18:19:27 +0200 [thread overview]
Message-ID: <44F3178F.8010508@linux.intel.com> (raw)
In-Reply-To: <20060828161145.GA25161@rhlx01.fht-esslingen.de>
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...
next prev parent reply other threads:[~2006-08-28 16:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 15:48 [PATCH] maximum latency tracking infrastructure (version 3) Arjan van de Ven
2006-08-28 16:11 ` Andreas Mohr
2006-08-28 16:19 ` Arjan van de Ven [this message]
2006-08-28 16:27 ` Andi Kleen
2006-08-28 16:35 ` Andreas Mohr
2006-08-28 16:48 ` Arjan van de Ven
2006-08-28 16:25 ` Jesse Barnes
2006-08-28 16:25 ` Arjan van de Ven
2006-08-28 16:30 ` Jesse Barnes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44F3178F.8010508@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=akpm@osdl.org \
--cc=andi@rhlx01.fht-esslingen.de \
--cc=dwalker@mvista.com \
--cc=jesse.barnes@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.