From: "Theodore Ts'o" <tytso@mit.edu>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux-kernel@vger.kernel.org, tony@atomide.com,
tuukka.tikkanen@elektrobit.com, ck@vds.kolivas.org
Subject: Re: [patch] i386 dynamic ticks 2.6.13-rc4 (code reordered)
Date: Sat, 6 Aug 2005 10:54:18 -0400 [thread overview]
Message-ID: <20050806145418.GA16523@thunk.org> (raw)
In-Reply-To: <200508021443.55429.kernel@kolivas.org>
On Tue, Aug 02, 2005 at 02:43:55PM +1000, Con Kolivas wrote:
> This is a code reordered version of the dynamic ticks patch from Tony Lindgen
> and Tuukka Tikkanen - sorry about spamming your mail boxes with this, but
> thanks for the code. There is significant renewed interest by the lkml
> audience for such a feature which is why I'm butchering your code (sorry
> again if you don't like me doing this). The only real difference between your
> code and this patch is moving the #ifdef'd code out of code paths and putting
> it into dyn-tick specific files.
>
> This has slightly more build fixes than the last one I posted and boots and
> runs fine on my laptop. So far at absolute idle it appears this pentiumM 1.7
> is claiming to have _25%_ more battery life. I'll need to investigate further
> to see the real power savings.
Hi Con,
I had a chance to try out your patch (2.6.13-rc4-dtck-2.patch) and
using either the APIC or PIT timer, if dynamic tick is enabled, on my
laptop, this kicks up the bus mastering activity enough so that the
processor doesn't have a chance to enter the C4 state, and stays stuck
at C2. As a result, enabling dynamic tick _increases_ power
consumption by 20% on my T40 laptop (1.6 MHz Pentium M). I monitored
power utilization using pmstats-0.2, and used
/proc/acpi/processor/CPU/power to monitor bus mastering activity and the CPU C-states.
As soon as I disabled dynamic tick using:
echo 0 > /sys/devices/system/timer/timer0/dyn_tick_state
The number of ticks went up to 1024, bus mastering activity dropped to
zero, and the processor entered C4 state, and power utilization
dropped by 20%.
When I enabled dynamic tick using:
echo 1 > /sys/devices/system/timer/timer0/dyn_tick_state
The number of ticks dropped down to 60-70 HZ, bus mastering activity
jumpped up to being almost always active, and the processor stayed
stuck at C2 state, and power utilization climbed back up by 20%.
This was on a completely idle, freshly booted machine, without X
running and just a console login.
- Ted
next prev parent reply other threads:[~2005-08-06 14:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 4:43 [patch] i386 dynamic ticks 2.6.13-rc4 (code reordered) Con Kolivas
2005-08-02 5:35 ` [ck] " Michael Marineau
2005-08-02 5:49 ` Con Kolivas
2005-08-02 5:52 ` Lee Revell
2005-08-02 5:56 ` Con Kolivas
2005-08-02 6:24 ` Lee Revell
2005-08-02 7:17 ` Tony Lindgren
2005-08-02 7:39 ` Con Kolivas
2005-08-02 8:15 ` Tony Lindgren
2005-08-02 10:54 ` Con Kolivas
2005-08-02 11:31 ` Tony Lindgren
2005-08-02 12:04 ` Con Kolivas
2005-08-02 7:21 ` Tony Lindgren
2005-08-02 14:01 ` Avuton Olrich
2005-08-02 14:05 ` Con Kolivas
2005-08-06 14:54 ` Theodore Ts'o [this message]
2005-08-06 15:00 ` Con Kolivas
2005-08-08 5:43 ` Stefan Seyfried
2005-08-08 21:54 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2005-08-08 18:37 Pallipadi, Venkatesh
2005-08-10 6:44 ` Thomas Renninger
2005-08-10 6:57 ` Con Kolivas
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=20050806145418.GA16523@thunk.org \
--to=tytso@mit.edu \
--cc=ck@vds.kolivas.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony@atomide.com \
--cc=tuukka.tikkanen@elektrobit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox