From: Ville Herva <vherva@niksula.hut.fi>
To: "Grover, Andrew" <andrew.grover@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CPU throttling??
Date: Tue, 4 Feb 2003 00:31:05 +0200 [thread overview]
Message-ID: <20030203223104.GA1258@niksula.cs.hut.fi> (raw)
In-Reply-To: <F760B14C9561B941B89469F59BA3A84725A14A@orsmsx401.jf.intel.com>
On Mon, Feb 03, 2003 at 01:14:18PM -0800, you [Grover, Andrew] wrote:
> > From: Dave Jones [mailto:davej@codemonkey.org.uk]
> > Valdis.Kletnieks@vt.edu wrote:
> >
> > > It's conceivable that a CPU halted at 1.2Gz takes less
> > power than one
> > > at 1.6Gz - anybody have any actual data on this?
> > Alternately phrased,
> > > does CPU throttling save power over and above what the halt does?
> >
> > Given that most decent implementations scale voltage as well as
> > frequency, yes, a lower speed will save more power.
>
> You save the most power when the CPU is at the lowest voltage level, and
> in the deepest CPU sleep state (aka CPU C state).
>
> Throttling offers a linear power/perf tradeoff if your system doesn't
> have C state support (or if you aren't using it) but really it is
> preferable to keep the CPU at its nominal speed, get the work done
> sooner, and start sleeping right away. The quote above makes it sound
> like the voltage is scaled when throttling, and that isn't accurate -
> voltage is scaled when sleeping (to counteract leakage current), at
> least on modern Intel mobile processors.
Interesting.
So, what sw does one need for this CPU C state? Which kernels support it /
which patches are needed? 2.5 only?
Also, which CPUs support it? Am I out of luck with my measly 1.4 Celeron
Tualatin?
So far I've only been doing "Make CPU Idle calls when idle", which I gather
is far from optimal?
-- v --
v@iki.fi
next prev parent reply other threads:[~2003-02-03 22:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-03 21:14 Grover, Andrew
2003-02-03 21:18 ` Dave Jones
2003-02-03 21:41 ` John Bradford
2003-02-03 22:14 ` H. Peter Anvin
2003-02-03 22:31 ` Ville Herva [this message]
2003-02-04 10:22 ` Seamus
2003-02-04 10:31 ` John Bradford
2003-02-04 11:01 ` Seamus
-- strict thread matches above, loose matches on Subject: below --
2003-02-03 21:51 Grover, Andrew
2003-02-03 15:47 Joeri Belis
2003-02-03 16:55 ` CPU throttling?? Seamus
2003-02-03 17:00 ` Dave Jones
2003-02-03 17:04 ` Martin Hermanowski
2003-02-03 17:13 ` John Bradford
2003-02-03 18:57 ` Valdis.Kletnieks
2003-02-03 19:02 ` Dave Jones
2003-02-03 19:09 ` Martin Hermanowski
2003-02-03 19:20 ` John Bradford
2003-02-04 14:12 ` Erik Mouw
2003-02-03 19:14 ` Matt Reppert
2003-02-03 19:24 ` Valdis.Kletnieks
2003-02-04 14:34 ` Daniel Egger
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=20030203223104.GA1258@niksula.cs.hut.fi \
--to=vherva@niksula.hut.fi \
--cc=andrew.grover@intel.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®