From: John Bradford <john@grabjohn.com>
To: martin@martin.mh57.de (Martin Hermanowski)
Cc: Valdis.Kletnieks@vt.edu, assembly@gofree.indigo.ie,
linux-kernel@vger.kernel.org
Subject: Re: CPU throttling??
Date: Mon, 3 Feb 2003 19:20:34 +0000 (GMT) [thread overview]
Message-ID: <200302031920.h13JKZZd001140@darkstar.example.net> (raw)
In-Reply-To: <20030203190920.GO1472@martin.mh57.de> from "Martin Hermanowski" at Feb 03, 2003 08:09:20 PM
> > > Incidently, Linux has always halted the processor, rather than spun in
> > > an idle loop, which saves power.
> >
> > 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?
>
> If I slow down my 1GHz CPU to 732MHz, I get 15min more (195min total).
> So it is not much, but noticeable.
Does anybody have any data on frequency throttling on non-X86
architectures?
John.
next prev parent reply other threads:[~2003-02-03 19:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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
2003-02-04 10:22 ` Seamus
2003-02-04 10:31 ` John Bradford
2003-02-04 11:01 ` Seamus
2003-02-03 21:51 Grover, Andrew
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=200302031920.h13JKZZd001140@darkstar.example.net \
--to=john@grabjohn.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=assembly@gofree.indigo.ie \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@martin.mh57.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 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.