mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: Matt Mackall <mpm@selenic.com>, Chodorenko Michail <misha@one.by>,
	linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Celeron Core
Date: Sun, 20 Jan 2008 12:18:40 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0801201216520.28200@anakin> (raw)
In-Reply-To: <20080119042750.GA24481@one.firstfloor.org>

On Sat, 19 Jan 2008, Andi Kleen wrote:
> > So while throttling may be less efficient in terms of watt seconds used
> > to compile something than running at full speed, it is incorrect to say
> > it uses less power. One machine running for an hour throttled to 50%
> > uses less power (and therefore less battery and cooling) than another
> > running at full speed for that same hour.
> 
> Not for the same unit of work. If you just run endless loops you 
> might be true, but most systems don't do that. 

So you mean energy (measured in J).
Power is energy/time unit (measured in W, i.e. J/s).

So I guess what you really want to say is: throttling decreases power
consumption, but on modern CPUs it increases the amount of energy needed
to perform the task.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

  parent reply	other threads:[~2008-01-20 11:19 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
     [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
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=Pine.LNX.4.64.0801201216520.28200@anakin \
    --to=geert@linux-m68k.org \
    --cc=andi@firstfloor.org \
    --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®