From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Bruno Ducrot <ducrot@poupinou.org>
Cc: CPUFreq@lists.linux.org.uk, davej@redhat.com
Subject: Re: [PATCH 2.6.14] cpufreq: don't suggest speedstep-centrino for Dothan-based Celeron-M processors
Date: Tue, 6 Dec 2005 07:01:49 +0100 [thread overview]
Message-ID: <20051206060149.GA4722@isilmar.linta.de> (raw)
In-Reply-To: <20051205110012.GA12747@poupinou.org>
Hi,
On Mon, Dec 05, 2005 at 12:00:12PM +0100, Bruno Ducrot wrote:
> > Yes, exactly. In my TODO list for cpufreq, I still have this entry:
> > - [core] evaluate use of > 1 drivers at one time (CPUFREQ_THROTTLING,
> > CPUFREQ_SCALING)
>
> Yes, that's what I had in mind. But maybe we could at first make the
> distinction before being able to load more than one driver?
Yes, sure. However, only on the x86 I'm quite confident that the throttling
state is equivalent to the idle state, and therefore doesn't offer
_additional_ power savings (besides the effect discussed by Dave yesterday)
if the CPU load is lower than (1 - throttling_rate), IMO.
CPUFREQ_SCALING:
acpi-cpufreq
elanfreq
powernow-k{6,7,8}
speedstep-{smi,ich,centrino}
longrun
longhaul
CPUFREQ_THROTTLING:
p4-clockmod
gx-suspmod
The other architectures I'm not so familiar with, so this list is x86 only
at the moment.
Dominik
next prev parent reply other threads:[~2005-12-06 6:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 21:19 [PATCH 2.6.14] cpufreq: don't suggest speedstep-centrino for Dothan-based Celeron-M processors Pallipadi, Venkatesh
2005-12-04 16:46 ` Dominik Brodowski
2005-12-05 11:00 ` Bruno Ducrot
2005-12-06 6:01 ` Dominik Brodowski [this message]
2005-12-06 10:03 ` Bruno Ducrot
2005-12-06 10:10 ` Dominik Brodowski
-- strict thread matches above, loose matches on Subject: below --
2005-12-02 16:58 Pallipadi, Venkatesh
2005-12-02 19:29 ` Felix Braun
2005-12-02 21:06 ` Bruno Ducrot
2005-12-02 14:26 Pallipadi, Venkatesh
2005-12-02 14:52 ` Felix Braun
2005-12-02 15:04 ` Bruno Ducrot
2005-12-02 13:57 Felix Braun
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=20051206060149.GA4722@isilmar.linta.de \
--to=linux@dominikbrodowski.net \
--cc=CPUFreq@lists.linux.org.uk \
--cc=davej@redhat.com \
--cc=ducrot@poupinou.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