From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: hugang@soulinfo.com
Cc: Tony Lindgren <tony@atomide.com>,
linux-kernel@vger.kernel.org, "Pallipadi,
Venkatesh" <venkatesh.pallipadi@intel.com>,
Jonathan Corbet <corbet@lwn.net>, Pavel Machek <pavel@ucw.cz>,
Bernard Blackham <b-lkml@blackham.com.au>,
Christian Hesse <mail@earthworm.de>,
Zwane Mwaikambo <zwane@arm.linux.org.uk>
Subject: Re: [PATCH] Dynamic tick for x86 version 050610-1
Date: Tue, 19 Jul 2005 23:51:54 +1000 [thread overview]
Message-ID: <1121781115.14393.59.camel@gaston> (raw)
In-Reply-To: <20050719065122.GA5913@hugang.soulinfo.com>
On Tue, 2005-07-19 at 14:51 +0800, hugang@soulinfo.com wrote:
> On Sat, Jun 18, 2005 at 04:30:32PM +1000, Benjamin Herrenschmidt wrote:
> >
> > > I'm try to port it powerpc, Here is a patch.
> > >
> > > Port Dynamic Tick Timer to new platform is easy. :)
> > > 1) Find the reprogram timer interface.
> > > 2) do a hook in the idle function.
> > >
> > > That worked on my PowerBookG4 12'.
> >
> > Did you get a measurable gain on power consumption ?
> >
> > Last time I toyed with this, I didn't.
>
> Today I do a measurable about it.
>
> First I using 2.6.12 without dynamic enable and unplug the AC power,
> I check the /proc/pmu/battery_0, like this.
> --
> flags : 00000011
> charge : 907
> max_charge : 2863
> current : -987
> voltage : 10950
> time rem. : 3600
> --
> I only intresting with current, that show the system power load.
>
> When I enable dynamic, The current can low at -900.
The numbers are repeatable ? I mean, if you actually let it settle down
in both cases ? Also, you should be careful about "parasites" in the
measurement, like pbbuttons dimming the backlight, the hard disk going
to sleep etc...
>From your numbers you get something like 10% improvement, which isn't
too bad.
Ben.
next prev parent reply other threads:[~2005-07-19 13:57 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-02 1:36 [PATCH] Dynamic tick for x86 version 050602-1 Tony Lindgren
2005-06-02 1:54 ` Zwane Mwaikambo
2005-06-02 2:09 ` Tony Lindgren
2005-06-02 8:30 ` Christian Hesse
2005-06-02 17:42 ` [PATCH] Dynamic tick for x86 version 050602-2 Tony Lindgren
2005-06-02 20:03 ` Christian Hesse
2005-06-02 20:32 ` Tony Lindgren
2005-06-03 6:08 ` Christian Hesse
2005-06-03 17:39 ` Tony Lindgren
2005-06-04 12:51 ` Christian Hesse
2005-06-10 4:03 ` Tony Lindgren
2005-06-05 4:06 ` Bernard Blackham
2005-06-10 4:05 ` Tony Lindgren
2005-06-03 22:37 ` Pavel Machek
2005-06-03 22:47 ` Pavel Machek
2005-06-10 4:17 ` Tony Lindgren
2005-06-10 9:15 ` Pavel Machek
2005-06-10 15:17 ` Tony Lindgren
2005-06-10 22:15 ` [PATCH] Dynamic tick for x86 version 050610-1 Tony Lindgren
2005-06-18 3:34 ` hugang
2005-06-18 6:30 ` Benjamin Herrenschmidt
2005-06-21 1:28 ` Tony Lindgren
2005-06-21 1:49 ` Benjamin Herrenschmidt
2005-06-21 2:21 ` Tony Lindgren
2005-07-19 6:51 ` hugang
2005-07-19 13:51 ` Benjamin Herrenschmidt [this message]
2005-07-25 10:11 ` Tony Lindgren
2005-06-11 17:59 ` [PATCH] Dynamic tick for x86 version 050602-2 Kyle Moffett
2005-06-07 20:36 ` [PATCH] Dynamic tick for x86 version 050602-1 Jonathan Corbet
2005-06-10 4:18 ` Tony Lindgren
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=1121781115.14393.59.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=b-lkml@blackham.com.au \
--cc=corbet@lwn.net \
--cc=hugang@soulinfo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@earthworm.de \
--cc=pavel@ucw.cz \
--cc=tony@atomide.com \
--cc=venkatesh.pallipadi@intel.com \
--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