mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Osterlund <petero2@telia.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Peter Osterlund <petero2@telia.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Zwane Mwaikambo <zwane@linuxpower.ca>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.19-rc1-ac3
Date: 13 Jul 2002 22:56:07 +0200	[thread overview]
Message-ID: <m2n0sv2vq0.fsf@best.localdomain> (raw)
In-Reply-To: <20020713205422.E25995@flint.arm.linux.org.uk>

Russell King <rmk@arm.linux.org.uk> writes:

> On Sat, Jul 13, 2002 at 09:43:16PM +0200, Peter Osterlund wrote:
> > So, is any of the above true for x86 processors? Or are there other
> > reasons to expect frequency scaling to increase battery run-time.
> 
> You're right if your CPU usage is 100% - lowering the CPU clock rate
> means you take longer to complete the task, and with the static
> element of the CPU power consumption, you'd probably end up using
> more energy to perform the same task in a longer time.
> 
> However, if, like most desktops, your CPU is sitting around 90% idle,
> if you lower the CPU clock rate, the idle time will drop.  Since the
> power drops, the rate at which the CPU uses energy also drops.
> However, overall your task completes in the same amount of time.

Hmm, assume my activity at the computer requires 10% CPU time when the
CPU is at full speed. My power consumption will then be

        P_fullspeed = P_static + 0.9 * P_idle_hi + 0.1 * P_busy_hi

If I halve the clock frequency, the computer will require 20% CPU time
to perform the work, and the power consumption becomes

        P_halfspeed = P_static + 0.8 * P_idle_lo + 0.2 * P_busy_lo

If the voltage doesn't change, 0.1 * P_busy_hi == 0.2 * P_busy_lo, so
the power savings will be

        P_fullspeed - P_halfspeed = 0.9 * P_idle_hi - 0.8 * P_idle_lo

or
        deltaP = 0.1 * P_idle_hi + 0.8 * (P_idle_hi - P_idle_lo)

The first term will be smaller the more idle my CPU is. (When reading
mail, I think 99% idle time is closer to the truth than 90%). The
second term in this formula is the reason I wondered if the power
consumption in apm idle mode is lower at lower clock frequencies.

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

  reply	other threads:[~2002-07-13 20:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-12 19:14 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
2002-07-13 19:54               ` Russell King
2002-07-13 20:56                 ` Peter Osterlund [this message]
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=m2n0sv2vq0.fsf@best.localdomain \
    --to=petero2@telia.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    --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

all inboxes | Powered by JetHome®