From: Avuton Olrich <avuton@gmail.com>
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: Tue, 2 Aug 2005 07:01:20 -0700 [thread overview]
Message-ID: <3aa654a40508020701e605533@mail.gmail.com> (raw)
In-Reply-To: <200508021443.55429.kernel@kolivas.org>
On 8/1/05, Con Kolivas <kernel@kolivas.org> 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.
OK, I rolled my own patch, 2.6.13-rc4-ck1-reiser4+this patch and it
appears to be running on my desktop Asus A7N8X very well:
I am running with Local APIC/IO-APIC/APIC Timer and forceapic. Time
does not appear to be running slow, and I do not appear to have a slow
boot.
sbh@rocket ~ $ cat /sys/devices/system/timer/timer0/dyn_tick_state
suitable: 1
enabled: 1
using APIC: 1
[4294683.959000] dyn-tick: Maximum ticks to skip limited to 803
[4294683.959000] dyn-tick: Timer using dynamic tick
The nvidia driver also works, and the most unexpected thing is after a
few hours of running it seems stable :)
So, to repeat I'm only reporting sucess, I'm unsure of the power
savings but this computer is on all day.
Thanks,
avuton
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2005-08-02 14:01 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 [this message]
2005-08-02 14:05 ` Con Kolivas
2005-08-06 14:54 ` Theodore Ts'o
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=3aa654a40508020701e605533@mail.gmail.com \
--to=avuton@gmail.com \
--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