linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: David Newall <davidn@davidnewall.com>
Cc: 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 06:42:02 +0100	[thread overview]
Message-ID: <20080120054202.GA19861@one.firstfloor.org> (raw)
In-Reply-To: <4792DADD.70504@davidnewall.com>

On Sun, Jan 20, 2008 at 03:53:41PM +1030, David Newall wrote:
> Andi Kleen wrote:
> >> Isn't it the case that an idle machine will use
> >> less power when throttled than when not?
> >>     
> >
> > No that is not the case (not even on old CPUs) 
> >   
> Then why would it run cooler?  

Ok for one more (but last) time:

Throttling just lowers the short term heat spikes to prevent
short term damage to the silicon.  For that it focusses on lowering 
the absolute temperature at a given point.  That only applies
when the CPU is busy.

But for total power consumption (or rather more concretly conserving
your battery) you don't care about absolute temperature at a given point
(as long as it is not high enough that it destroys the CPU)
you care about how much power is consumed (and heat generated from that) 
averaged out over a longer time.

And for most typical workloads (not running endless loops; significant
idle time) throttling makes no difference and in fact often (especially
on laptop CPUs with deeper sleep modi like the original reported
had one) makes it likely worse (see previous mails for details why) 

> I'm not convinced.  I'm along way from that.

Frankly that's fine for me. I don't really feel any need to convince you. 
I can live with your metal model of CPU physics not being accurate.

-Andi (feeling a bit like a broken record) 
> 

  reply	other threads:[~2008-01-20  5:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-18 19:06 PROBLEM: Celeron Core 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 [this message]
2008-01-20 20:53                     ` Lennart Sorensen
2008-01-20 11:18           ` Geert Uytterhoeven
     [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
  -- strict thread matches above, loose matches on Subject: below --
2008-01-20 22:06 Tomasz Chmielewski
2008-01-20 22:26 ` Rafael J. Wysocki
2008-01-21 10:11 ` Matthew Garrett
     [not found] <fa.tHyDHqRNYFvp4N4SR4JtJRuqh0k@ifi.uio.no>
2008-01-21 23:59 ` Robert Hancock

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=20080120054202.GA19861@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=davidn@davidnewall.com \
    --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;
as well as URLs for NNTP newsgroup(s).