public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ondrej Zajicek <santiago@crfreenet.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: david@lang.hm, Igor Stoppa <igor.stoppa@nokia.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-pm <linux-pm@lists.linux-foundation.org>
Subject: Re: [linux-pm] Power Management framework proposal
Date: Mon, 23 Jul 2007 10:56:36 +0200	[thread overview]
Message-ID: <20070723085636.GA4123@localhost.localdomain> (raw)
In-Reply-To: <1185164357.2714.49.camel@laptopd505.fenrus.org>

On Sun, Jul 22, 2007 at 09:19:17PM -0700, Arjan van de Ven wrote:
> let me give you a real world example then, and the numbers I'm using are
> ballpark the same as you'll find in a (mobile) core 2 duo datasheet, I
> just rounded them a little so that the math works out nice.
> 
> power at full speed: 34W
> power at half speed: 24W
> power at idle: 1W

I have usually seen different numbers, for example:

http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/30430.pdf

Although this paper speaks about thermal design power instead of power
consumption, i suppose that it should be roughly equal.

For example Athlon 64 3700 (ADA3700AEP5AR):

2.4 GHz, 1.5 V -> 89 W
2.2 GHz, 1.4 V -> 72 W
2.0 GHz, 1.3 V -> 53 W
1.8 GHz, 1.2 V -> 39 W
1.0 GHz, 1.1 V -> 22 W


Even my measurement on PC (Athlon X2, VIA K8T890) of complete PC power
consumption shows that it is more efficient to be busy for 2 time units
on 1 GHz than be busy for 1 time unit and be idle for 1 time unit
on 2 GHz.

1 GHz:
both cores idle:	48 W
one core busy:		57 W
two cores busy:		66 W

2 GHz:
both cores idle:	54 W
one core busy:		78 W
two cores busy:		95 W

-- 
Elen sila lumenn' omentielvo

Ondrej 'SanTiago' Zajicek (email: santiago@crfreenet.org, jabber: santiago@njs.netlab.cz)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."

  parent reply	other threads:[~2007-07-23  8:58 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-22  6:49 Power Management framework proposal david
2007-07-22  7:57 ` [linux-pm] " Igor Stoppa
2007-07-22  8:58   ` david
2007-07-22 12:05     ` Igor Stoppa
2007-07-22 21:21       ` david
2007-07-22 23:09         ` Arjan van de Ven
2007-07-23  2:45           ` david
2007-07-23  3:50             ` Arjan van de Ven
2007-07-23  4:04               ` david
2007-07-23  4:19                 ` Arjan van de Ven
2007-07-23  5:25                   ` david
2007-07-23 14:12                     ` Arjan van de Ven
2007-07-23 18:19                       ` david
2007-07-23  8:56                   ` Ondrej Zajicek [this message]
2007-07-23 17:33                     ` david
2007-07-27 12:04                     ` Pavel Machek
2007-07-23 10:48         ` Igor Stoppa
2007-07-23 18:14           ` david
2007-07-24  8:43             ` Jerome Glisse
2007-07-24 14:18               ` Igor Stoppa
2007-07-24 20:13                 ` david
2007-07-24 20:06               ` david
2007-07-24 23:14                 ` Jerome Glisse
2007-07-25  0:40                   ` david
2007-07-25 12:49                     ` Jerome Glisse
2007-07-29 21:56                       ` david
2007-07-22 17:26 ` Arjan van de Ven
2007-07-22 18:56   ` david
2007-07-22 22:27     ` Arjan van de Ven
2007-07-23  3:51       ` david
2007-07-23  4:00         ` Arjan van de Ven
2007-07-23  4:09           ` david
2007-07-27 11:46             ` Pavel Machek
2007-07-29 22:00               ` david
2007-07-30  1:05                 ` Matthew Garrett
2007-07-23 22:23   ` Benjamin Herrenschmidt
2007-07-24 20:14     ` david
2007-07-24 21:38       ` Benjamin Herrenschmidt
2007-07-24 23:02         ` david
2007-07-24 23:47           ` Benjamin Herrenschmidt

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=20070723085636.GA4123@localhost.localdomain \
    --to=santiago@crfreenet.org \
    --cc=arjan@infradead.org \
    --cc=david@lang.hm \
    --cc=igor.stoppa@nokia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.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