From: Pavel Machek <pavel@suse.cz>
To: Thomas Renninger <trenn@suse.de>
Cc: Tony Lindgren <tony@atomide.com>,
Frank Sorenson <frank@tuxrocks.com>,
linux-kernel@vger.kernel.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Arjan van de Ven <arjan@infradead.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Andrea Arcangeli <andrea@suse.de>,
George Anzinger <george@mvista.com>,
Thomas Gleixner <tglx@linutronix.de>,
john stultz <johnstul@us.ibm.com>,
Zwane Mwaikambo <zwane@arm.linux.org.uk>,
Lee Revell <rlrevell@joe-job.com>,
ML ACPI-devel <acpi-devel@lists.sourceforge.net>,
Bodo Bauer <bb@suse.de>, Andi Kleen <ak@suse.de>
Subject: Re: [PATCH] Updated: Dynamic Tick version 050408-1 - C-state measures
Date: Tue, 19 Apr 2005 23:09:58 +0200 [thread overview]
Message-ID: <20050419210958.GE25328@elf.ucw.cz> (raw)
In-Reply-To: <42651C38.6090807@suse.de>
Hi!
> The machine is a Pentium M 2.00 GHz, supporting C0-C4 processor power states.
> The machine run at 2.00 GHz all the time.
..
> _passing bm_history=0xFFFFFFFF (default) to processor module:_
>
> Average current the last 470 seconds: *1986mA* (also measured better
> values ~1800, does battery level play a role?!?)
Probably yes. If voltage changes, 2000mA means different ammount of power.
> (cmp. ftp://ftp.suse.com/pub/people/trenn/dyn_tick_c_states/measures_C4_machine/1000_HZ_bm_history_FFFFFFFF)
>
>
> _passing bm_history=0xFF to processor module:_
>
> Average current the last 190 seconds: *1757mA*
> (cmp. ftp://ftp.suse.com/pub/people/trenn/dyn_tick_c_states/measures_C4_machine/1000_HZ_bm_history_FF)
> (Usage count could be bogus, as some invokations could not succeed
> if bm has currently been active).
Ok.
> idle_ms == 100, bm_promote_bs == 30
> Average current the last 80 seconds: *1466mA*
> (cmp.
> ftp://ftp.suse.com/pub/people/trenn/dyn_tick_c_states/measures_C4_machine/tony_dyn_tick_processor_idle_100_bm_30)
Very nice indeed. That seems like ~5W saved, right? That might give
you one more hour of battery life....
Pavel
--
Boycott Kodak -- for their patent abuse against Java.
next prev parent reply other threads:[~2005-04-19 21:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050406083000.GA8658@atomide.com>
[not found] ` <425451A0.7020000@tuxrocks.com>
[not found] ` <20050407082136.GF13475@atomide.com>
[not found] ` <4255A7AF.8050802@tuxrocks.com>
[not found] ` <4255B247.4080906@tuxrocks.com>
[not found] ` <20050408062537.GB4477@atomide.com>
[not found] ` <20050408075001.GC4477@atomide.com>
[not found] ` <42564584.4080606@tuxrocks.com>
[not found] ` <42566C22.4040509@suse.de>
[not found] ` <20050408115535.GI4477@atomide.com>
2005-04-19 14:56 ` [PATCH] Updated: Dynamic Tick version 050408-1 - C-state measures Thomas Renninger
2005-04-19 15:27 ` Dominik Brodowski
2005-04-19 21:03 ` Thomas Renninger
2005-04-20 11:44 ` Dominik Brodowski
2005-04-20 11:57 ` Pavel Machek
2005-04-20 12:01 ` Dominik Brodowski
2005-04-20 12:08 ` Pavel Machek
2005-04-20 12:13 ` Dominik Brodowski
2005-04-20 12:24 ` Thomas Renninger
2005-04-19 21:09 ` Pavel Machek [this message]
2005-04-20 20:01 ` Tony Lindgren
2005-04-21 7:54 ` Thomas Renninger
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=20050419210958.GE25328@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=acpi-devel@lists.sourceforge.net \
--cc=ak@suse.de \
--cc=andrea@suse.de \
--cc=arjan@infradead.org \
--cc=bb@suse.de \
--cc=benh@kernel.crashing.org \
--cc=frank@tuxrocks.com \
--cc=george@mvista.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=schwidefsky@de.ibm.com \
--cc=tglx@linutronix.de \
--cc=tony@atomide.com \
--cc=trenn@suse.de \
--cc=zwane@arm.linux.org.uk \
/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