From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: david@lang.hm, LKML <linux-kernel@vger.kernel.org>,
linux-pm <linux-pm@lists.linux-foundation.org>
Subject: Re: Power Management framework proposal
Date: Tue, 24 Jul 2007 08:23:25 +1000 [thread overview]
Message-ID: <1185229405.5439.148.camel@localhost.localdomain> (raw)
In-Reply-To: <1185125189.2714.13.camel@laptopd505.fenrus.org>
On Sun, 2007-07-22 at 10:26 -0700, Arjan van de Ven wrote:
> On Sat, 2007-07-21 at 23:49 -0700, david@lang.hm wrote:
>
> > this approach would allow the transition of ALL drivers to the new mode of
> > operation in one fell swoop, and then adding additional power management
> > features is just adding to the existing list rather then implementing new
> > functions.
>
>
> I have a concern with this approach though. It seems to assume that
> there is one global thing somewhere that sets the system state; in my
> experience that is the wrong approach; in fact there is a very definite
> evidence that there are many decisions on power that are to be made
> local at a high frequency. An example of this is the processor speed;
> the ondemand governer does exactly this for the cpus that can switch
> speeds fast; it's just impossible to beat such a local, fast decision
> with anything on a global scale.
>
> On the other hand, some things (the high level goals and constraints)
> are obviously global.
I think we need a set of constraints that trickle down the power tree
and limit what a given driver can do locally.
Ben.
next prev parent reply other threads:[~2007-07-23 22:24 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-22 6:49 david
2007-07-22 7:57 ` [linux-pm] " Igor Stoppa
2007-07-22 8:58 ` david
2007-07-22 12:05 ` Igor Stoppa
2007-07-22 21:21 ` david
2007-07-22 23:09 ` Arjan van de Ven
2007-07-23 2:45 ` david
2007-07-23 3:50 ` Arjan van de Ven
2007-07-23 4:04 ` david
2007-07-23 4:19 ` Arjan van de Ven
2007-07-23 5:25 ` david
2007-07-23 14:12 ` Arjan van de Ven
2007-07-23 18:19 ` david
2007-07-23 8:56 ` Ondrej Zajicek
2007-07-23 17:33 ` david
2007-07-27 12:04 ` Pavel Machek
2007-07-23 10:48 ` Igor Stoppa
2007-07-23 18:14 ` david
2007-07-24 8:43 ` Jerome Glisse
2007-07-24 14:18 ` Igor Stoppa
2007-07-24 20:13 ` david
2007-07-24 20:06 ` david
2007-07-24 23:14 ` Jerome Glisse
2007-07-25 0:40 ` david
2007-07-25 12:49 ` Jerome Glisse
2007-07-29 21:56 ` david
2007-07-22 17:26 ` Arjan van de Ven
2007-07-22 18:56 ` david
2007-07-22 22:27 ` Arjan van de Ven
2007-07-23 3:51 ` david
2007-07-23 4:00 ` Arjan van de Ven
2007-07-23 4:09 ` david
2007-07-27 11:46 ` Pavel Machek
2007-07-29 22:00 ` david
2007-07-30 1:05 ` Matthew Garrett
2007-07-23 22:23 ` Benjamin Herrenschmidt [this message]
2007-07-24 20:14 ` david
2007-07-24 21:38 ` Benjamin Herrenschmidt
2007-07-24 23:02 ` david
2007-07-24 23:47 ` Benjamin Herrenschmidt
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=1185229405.5439.148.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=arjan@infradead.org \
--cc=david@lang.hm \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome