From: Voluspa <lista1@comhem.se>
To: Daniel Walker <dwalker@mvista.com>
Cc: brugolsky@telemetry-investments.com, mingo@elte.hu,
pavel@suse.cz, akpm@osdl.org, tglx@linutronix.de,
linux-kernel@vger.kernel.org
Subject: Re: hires timer patchset [was Re: 2.6.19 -mm merge plans]
Date: Sat, 23 Sep 2006 21:22:25 +0200 [thread overview]
Message-ID: <20060923212225.060bb5f7@loke.fish.not> (raw)
In-Reply-To: <1159034967.21405.22.camel@c-67-180-230-165.hsd1.ca.comcast.net>
On Sat, 23 Sep 2006 11:09:26 -0700 Daniel Walker wrote:
> On Sat, 2006-09-23 at 04:17 +0200, Voluspa wrote:
>
> > Here's another data point: I tried 2.6.18-rt3 today on a x86_64
> > notebook. I'm on an eternal quest for extended battery time, so
> > NO_HZ would be perfect. Long story shortened, HIGH_RES_TIMERS
> > (prerequisite for NO_HZ) caused the CPU to never step down from max
> > speed (ondemand, powernow_k8) at 2200 MHz.
> >
> > In addition, something invisible used very frequent bursts of ~30%
> > SYS CPU. Turning from PREEMPT_RT to PREEMPT_DESKTOP introduced
> > occasional bursts of ~50% USER CPU (mixed with the SYS). Toggling
> > RCU model made no difference.
> >
>
> It seems like you don't need all of 2.6.18-rt3 , you just want dynamic
> tick .. You can obtain just the HRT/dynamic tick patch from here,
>
> http://www.tglx.de/projects/hrtimers/2.6.18/
Thank you pointing that out. I didn't realise that the features were so
sharply divided. Perhaps I'll even be able to debug it locally, then -
wearing ear-mufflers. I'm not kidding about the fan noise.
At the very least the experiment will tell if it's a -rt combo problem
or NO_HZ on its own.
Mvh
Mats Johannesson
next prev parent reply other threads:[~2006-09-23 19:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-23 2:17 hires timer patchset [was Re: 2.6.19 -mm merge plans] Voluspa
2006-09-23 18:09 ` Daniel Walker
2006-09-23 19:22 ` Voluspa [this message]
2006-09-23 19:58 ` Voluspa
2006-09-23 20:20 ` Ingo Molnar
2006-09-24 2:36 ` Voluspa
-- strict thread matches above, loose matches on Subject: below --
2006-09-23 15:25 Voluspa
2006-09-23 16:34 ` Andi Kleen
2006-09-25 11:18 ` Arjan van de Ven
2006-09-20 20:54 2.6.19 -mm merge plans Andrew Morton
2006-09-21 13:14 ` Ingo Molnar
2006-09-22 13:06 ` Pavel Machek
2006-09-22 19:01 ` Ingo Molnar
2006-09-22 20:29 ` hires timer patchset [was Re: 2.6.19 -mm merge plans] Bill Rugolsky Jr.
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=20060923212225.060bb5f7@loke.fish.not \
--to=lista1@comhem.se \
--cc=akpm@osdl.org \
--cc=brugolsky@telemetry-investments.com \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pavel@suse.cz \
--cc=tglx@linutronix.de \
/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.