cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@brodo.de>
To: Jan Rychter <jan@rychter.com>
Cc: Mukesh Rajan <megabyte1024@hotmail.com>,
	cpufreq@www.linux.org.uk, linux-acpi <linux-acpi@intel.com>
Subject: Re: [PATCHSET] 0/3 Dynamic cpufreq governor and updates to ACPI P-state driver
Date: Tue, 4 Nov 2003 08:16:38 +0100	[thread overview]
Message-ID: <20031104071638.GA4126@brodo.de> (raw)
In-Reply-To: <m24qxk4y4h.fsf@tnuctip.rychter.com>

On Mon, Nov 03, 2003 at 07:21:34PM -0800, Jan Rychter wrote:
> >>>>> "Len" == Len Brown writes:
>  >> I have done some measurements on a Toshiba S7/290LNKW, which has a
>  >> 900MHz Pentium-M. The results have been posted to this list a while
>  >> ago -- the most surprising one being that the Pentium-M in that
>  >> machine seemed to always consume the same amount of power when idle,
>  >> independent of operating frequency.  The frequency only made a
>  >> difference when the CPU was actually doing something (or when I made
>  >> it not use the C3 state by loading usb-uhci).
> 
>  Len> Probably the cpu is running HLT in the idle loop, so the power
>  Len> consumption there would not vary with MHz.
> 
> Oh -- well, that's exactly what I wanted to check. It seems it does vary
> for speedstepped Pentium-III Mobile, according to my measurements,
> that's why I was surprised.
> 
> This should influence the design of dynamic power management -- if the
> CPU is already idle, there is no point in slowing it down. It only makes
> sense to change the frequency when we're actually doing something.

This assumption is at least partly wrong. Pentium-III Mobile datasheets
clearly show that the power usage when doing nothing varies up to 50%
dependand on the frequency setting. So even if it is no measurable effect on
one processor, this theory isn't true for all processors. And dynamic
power management should work best _for all processors_.

	Dominik

  reply	other threads:[~2003-11-04  7:16 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-04  3:14 [PATCHSET] 0/3 Dynamic cpufreq governor and updates to ACPI P-state driver Brown, Len
2003-11-04  3:21 ` Jan Rychter
2003-11-04  7:16   ` Dominik Brodowski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-05 21:12 Mukesh Rajan
2003-10-22 18:21 Pallipadi, Venkatesh
2003-10-23  8:19 ` Arjan van de Ven
2003-10-23  8:24   ` Alexander Bokovoy
2003-10-23  8:29     ` Arjan van de Ven
2003-10-23 18:03       ` Ducrot Bruno
2003-10-23 18:16   ` Todd Poynor
2003-10-23 18:26     ` Todd Poynor
2003-11-02 20:28 ` Jan Rychter
2003-10-22  1:48 Pallipadi, Venkatesh
2003-10-22  1:42 Pallipadi, Venkatesh
2003-10-21  2:56 Pallipadi, Venkatesh
2003-10-21  8:25 ` Måns Rullgård
2003-10-21 20:47   ` Dominik Brodowski
2003-10-21 10:57 ` Måns Rullgård
2003-10-21 11:09   ` Måns Rullgård
2003-10-21 20:30   ` Alexander Bokovoy
2003-10-21 20:39     ` Måns Rullgård
2003-10-21 21:11       ` Alexander Bokovoy
2003-10-21 21:37         ` Måns Rullgård
2003-10-21 21:53           ` Alexander Bokovoy
2003-10-21 22:27             ` Måns Rullgård

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=20031104071638.GA4126@brodo.de \
    --to=linux@brodo.de \
    --cc=cpufreq@www.linux.org.uk \
    --cc=jan@rychter.com \
    --cc=linux-acpi@intel.com \
    --cc=megabyte1024@hotmail.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