From: Hollis Blanchard <hollis@austin.ibm.com>
To: Dominik Brodowski <linux@brodo.de>
Cc: Arjan van de Ven <arjanv@redhat.com>,
Bishop Brock <bcbrock@us.ibm.com>,
linux-kernel@vger.kernel.org,
cpufreq list <cpufreq@www.linux.org.uk>,
linux-pm-devel@lists.sourceforge.net
Subject: Re: [Linux-pm-devel] Re: IBM/MontaVista Dynamic Power Management Project
Date: 03 Dec 2002 14:31:12 -0600 [thread overview]
Message-ID: <1038947473.1249.217.camel@granite.austin.ibm.com> (raw)
In-Reply-To: <20021203200019.GD1340@brodo.de>
[-- Attachment #1: Type: text/plain, Size: 1423 bytes --]
On Tue, 2002-12-03 at 14:00, Dominik Brodowski wrote:
> On Tue, Dec 03, 2002 at 12:27:03PM -0600, Hollis Blanchard wrote:
> > On Tue, 2002-12-03 at 11:57, Arjan van de Ven wrote:
> > >
> > > any idea if/how this will fit into the existing cross platform cpufreq
> > > framework ?
> >
> > It subsumes it, similar to Dominik's ideas in "[RFC] Dynamic Frequency
> > and Voltage Scaling Infrastructure" (on the cpufreq list). The idea is
> > that you want scaling events to be generated by the kernel rather than
> > only scaling on userland input. The paper (and Dominik's mail) give you
> > some ideas of when and why...
>
> So, will it basically be a "policy governor" as described in my "[RFC]" mail?
> Or does it need other enhancements in the cpufreq core?
>
> BTW, have you noticed the premilinary patch I which implements most of the
> DVS infrastructure mentioned in my mail to the cpufreq list yesterday?
Honestly I haven't had time to read it over and compare and contrast
with the IBM paper. From the sound of things though, I suspect both your
patch and the IBM code implement the same thing: an infrastructure
allowing "governors" to control dynamic scaling. The 405LP code also
includes such a governor of course. The ideas may be almost identical;
I'm not sure anyone's compared at this point. Do you have the time? ;)
-Hollis
--
PowerPC Linux
IBM Linux Technology Center
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2002-12-03 20:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 17:46 Bishop Brock
2002-12-03 17:57 ` Arjan van de Ven
2002-12-03 18:27 ` [Linux-pm-devel] " Hollis Blanchard
2002-12-03 20:00 ` Dominik Brodowski
2002-12-03 20:31 ` Hollis Blanchard [this message]
2002-12-05 8:18 ` Dominik Brodowski
2002-12-03 18:39 ` Alan Cox
2002-12-03 18:45 ` [Linux-pm-devel] " Hollis Blanchard
2002-12-04 3:34 [Linux-pm-devel] " Bishop Brock
2002-12-05 8:48 ` Dominik Brodowski
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=1038947473.1249.217.camel@granite.austin.ibm.com \
--to=hollis@austin.ibm.com \
--cc=arjanv@redhat.com \
--cc=bcbrock@us.ibm.com \
--cc=cpufreq@www.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm-devel@lists.sourceforge.net \
--cc=linux@brodo.de \
/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
all inboxes | Powered by JetHome®