The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Peter Osterlund <petero2@telia.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Zwane Mwaikambo <zwane@linuxpower.ca>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.19-rc1-ac3
Date: 13 Jul 2002 21:43:16 +0200	[thread overview]
Message-ID: <m265zj9zxn.fsf@best.localdomain> (raw)
In-Reply-To: <1026584861.13886.27.camel@irongate.swansea.linux.org.uk>

Alan Cox <alan@lxorguk.ukuu.org.uk> writes:

> On Sat, 2002-07-13 at 17:22, Peter Osterlund wrote:
> > How much power savings can be expected in this situation? Is SpeedStep
> > likely to give more power savings?
> 
> Disregarding the fact that a large amount of your power consumption is
> 	LCD backlight
> 	Memory
> 	Disk spinning
> 
> the CPU (and to an extent thus the fan) part of the power consumption
> reduces approximately linearly with the clock speed drop and also the
> square of the voltage drop. There is an ever growing static component
> with newer chips but even so its quite measurable done right.

OK, but since frequency scaling saves power but not energy, unless you
also lower the voltage, can you expect the battery to last longer with
reduced frequency, assuming the computer is mostly idle? I guess the
answer would be yes if any of the following is true:

1. apm idle mode consumes less power at lower frequencies.

2. The lower clock frequency means less work gets done, for example
   because window updates become less frequent when moving windows.

3. The cpu voltage is automatically reduced when the frequency is
   reduced.

So, is any of the above true for x86 processors? Or are there other
reasons to expect frequency scaling to increase battery run-time.

-- 
Peter Osterlund - petero2@telia.com
http://w1.894.telia.com/~u89404340

  reply	other threads:[~2002-07-13 19:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-12 19:14 Linux 2.4.19-rc1-ac3 Alan Cox
2002-07-12 23:42 ` Peter Osterlund
2002-07-13  7:41   ` Zwane Mwaikambo
2002-07-13 10:34     ` Peter Osterlund
2002-07-13 12:38       ` Zwane Mwaikambo
2002-07-13 16:22         ` Peter Osterlund
2002-07-13 18:27           ` Alan Cox
2002-07-13 19:43             ` Peter Osterlund [this message]
2002-07-13 19:54               ` Russell King
2002-07-13 20:56                 ` Peter Osterlund
2002-07-15 10:13                 ` Thomas Sailer
2002-07-15 10:16                   ` Russell King
2002-07-14  1:50               ` Alan Cox
     [not found]               ` <6010.1026651788@www53.gmx.net>
2002-07-14 13:09                 ` Dominik Brodowski
2002-07-14 15:19                   ` Peter Osterlund
2002-07-14 15:50                     ` Dominik Brodowski
2002-07-14 18:52                       ` Peter Osterlund
2002-07-13 10:25   ` Peter Osterlund
2002-07-13 14:15 ` Pavel Machek
2002-07-13 17:09   ` Alan Cox
2002-07-13 15:59 ` fchabaud

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=m265zj9zxn.fsf@best.localdomain \
    --to=petero2@telia.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zwane@linuxpower.ca \
    /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