From: Andi Kleen <andi@firstfloor.org>
To: Robert Hancock <hancockr@shaw.ca>
Cc: David Newall <davidn@davidnewall.com>,
Andi Kleen <andi@firstfloor.org>, Matt Mackall <mpm@selenic.com>,
Chodorenko Michail <misha@one.by>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: Celeron Core
Date: Sun, 20 Jan 2008 20:16:43 +0100 [thread overview]
Message-ID: <20080120191643.GB28190@one.firstfloor.org> (raw)
In-Reply-To: <479391C9.9020004@shaw.ca>
> I believe that all throttling does is forcibly halt the CPU on a
> particular duty cycle. This will reduce the rate of power consumption,
> but reduces the CPU performance by a greater amount (since even at 100%
> halted the CPU still consumes power) and so actually reduces performance
> per watt. It will spread the heat and power usage produced from a given
> workload task out in time (thus its usefulness in limiting CPU
> temperature) but will consume more power overall.
...and more importantly deep sleep states in idle save far more power than
anything else and with throttling the CPU is idle shorter.
-Andi
next prev parent reply other threads:[~2008-01-20 19:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.2Y+LplM9PCtpiAXzv/aJ3Pcnv4Y@ifi.uio.no>
[not found] ` <fa.OpXJDCw416yeXEvt0cwrupi/qS0@ifi.uio.no>
[not found] ` <fa.sj34KNXkf9z/ZO3fVJ+CYcgcuCs@ifi.uio.no>
[not found] ` <fa.qpK4b5H7lkLeIaPtbJKzKV46yFY@ifi.uio.no>
[not found] ` <fa.WeBRuL3UPPVPESVzfopvVyNcAw4@ifi.uio.no>
[not found] ` <fa.LZLUxfR64dAZFPtin9JNet7ieiY@ifi.uio.no>
2008-01-20 18:24 ` Robert Hancock
2008-01-20 19:14 ` Matt Mackall
2008-01-20 19:24 ` Robert Hancock
2008-01-20 21:31 ` Rafael J. Wysocki
2008-01-21 7:48 ` Daniel Barkalow
2008-01-20 19:16 ` Andi Kleen [this message]
[not found] <fa.tHyDHqRNYFvp4N4SR4JtJRuqh0k@ifi.uio.no>
2008-01-21 23:59 ` Robert Hancock
2008-01-20 22:06 Tomasz Chmielewski
2008-01-20 22:26 ` Rafael J. Wysocki
2008-01-21 10:11 ` Matthew Garrett
-- strict thread matches above, loose matches on Subject: below --
2008-01-18 19:06 Chodorenko Michail
2008-01-18 21:11 ` Andi Kleen
2008-01-19 0:27 ` Matt Mackall
2008-01-19 1:15 ` Andi Kleen
2008-01-19 4:10 ` Matt Mackall
2008-01-19 4:27 ` Andi Kleen
2008-01-19 4:40 ` Matt Mackall
2008-01-19 4:54 ` Andi Kleen
2008-01-20 4:35 ` David Newall
2008-01-20 5:13 ` Andi Kleen
2008-01-20 5:23 ` David Newall
2008-01-20 5:42 ` Andi Kleen
2008-01-20 20:53 ` Lennart Sorensen
2008-01-20 11:18 ` Geert Uytterhoeven
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=20080120191643.GB28190@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=davidn@davidnewall.com \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=misha@one.by \
--cc=mpm@selenic.com \
/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®