From: Todd Poynor <tpoynor@mvista.com>
To: arjanv@redhat.com
Cc: linux-acpilinux-acpi@intel.com, cpufreq@www.linux.org.uk,
"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Subject: Re: [PATCHSET] 0/3 Dynamic cpufreq governor and updates to ACPI P-state driver
Date: Thu, 23 Oct 2003 11:16:48 -0700 [thread overview]
Message-ID: <3F981B10.3070900@mvista.com> (raw)
In-Reply-To: <1066897184.395.1.camel@laptop.fenrus.com>
[-- Attachment #1: Type: text/plain, Size: 1485 bytes --]
On Wed, 2003-10-22 at 20:21, Pallipadi, Venkatesh wrote:
>And with the kind of power savings that comes with these frequency
>changes, this behaviour
>results in longer battery life. However, as yet I do not have any
>numbers to quantify this gain,
>mainly because I do not have any setup where I can measure actual power.
I measured amps consumed by a 1.4GHz Centrino notebook model running a
similar power management system called Dynamic Power Management
http://dynamicpower.sourceforge.net, which leverages code from the
speedstep-centrino cpufreq driver by Jeremy Fitzhardinge. DPM is set to
run the system at full power when running a process and at minimal power
when idle (using scheduler hooks). These numbers, which are attached,
would probably roughly correspond to a cpufreq-based setup on the same
platform that modified the CPU speed and voltage very quickly in
response to process scheduling activity. I may perform some analysis of
more dynamic applications that more evenly divide their time between
active and idle in the near future, in case there is any interest in this.
Amps consumed should be a good predictor of expected battery life,
independent of the vagaries of any particular battery. The expensive
scopemeter used for the attached measurements isn't really necessary, by
the way; a $130 multimeter that averages DC amps, placed in series
between the DC transformer and the notebook, should do fine. In case
this helps,
--
Todd
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Cpufreq mailing list
Cpufreq@www.linux.org.uk
http://www.linux.org.uk/mailman/listinfo/cpufreq
next prev parent reply other threads:[~2003-10-23 18:16 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 18:21 [PATCHSET] 0/3 Dynamic cpufreq governor and updates to ACPI P-state driver 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 [this message]
2003-10-23 18:26 ` Todd Poynor
2003-11-02 20:28 ` Jan Rychter
-- strict thread matches above, loose matches on Subject: below --
2003-11-05 21:12 Mukesh Rajan
2003-11-04 3:14 Brown, Len
2003-11-04 3:21 ` Jan Rychter
2003-11-04 7:16 ` Dominik Brodowski
2003-10-22 1:48 Pallipadi, Venkatesh
2003-10-22 1:48 ` Pallipadi, Venkatesh
2003-10-22 1:42 Pallipadi, Venkatesh
2003-10-22 1:42 ` Pallipadi, Venkatesh
2003-10-21 2:56 Pallipadi, Venkatesh
2003-10-21 2:56 ` Pallipadi, Venkatesh
2003-10-21 8:25 ` Måns Rullgård
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=3F981B10.3070900@mvista.com \
--to=tpoynor@mvista.com \
--cc=arjanv@redhat.com \
--cc=cpufreq@www.linux.org.uk \
--cc=linux-acpilinux-acpi@intel.com \
--cc=venkatesh.pallipadi@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.