From: Con Kolivas <kernel@kolivas.org>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Lee Revell <rlrevell@joe-job.com>,
Alistair John Strachan <s0348365@sms.ed.ac.uk>,
Claudio Scordino <cloud.of.andor@gmail.com>,
linux-kernel@vger.kernel.org, kernelnewbies@nl.linux.org
Subject: Re: The "best" value of HZ
Date: Fri, 28 Oct 2005 14:29:39 +1000 [thread overview]
Message-ID: <200510281429.39532.kernel@kolivas.org> (raw)
In-Reply-To: <9a8748490510272100u453e73e3mc957a673eeb8498e@mail.gmail.com>
On Fri, 28 Oct 2005 02:00 pm, Jesper Juhl wrote:
> On 10/28/05, Lee Revell <rlrevell@joe-job.com> wrote:
> > On Fri, 2005-10-28 at 03:31 +0100, Alistair John Strachan wrote:
> > > On Friday 28 October 2005 00:18, Claudio Scordino wrote:
> > > > Hi,
> > > >
> > > > during the last years there has been a lot of discussion about
> > > > the "best" value of HZ... On i386 was 100, then became 1000, and
> > > > finally was set to 250. I'm thinking to do an evaluation of this
> > > > parameter using different architectures.
> > > >
> > > > Has anybody thought to give the possibility to modify the value of HZ
> > > > at boot time instead of at compile time ? This would allow to easily
> > > > test different values on different machines and create a table
> > > > containing the "best" value for each architecture... At this moment,
> > > > instead, we have to recompile the kernel for each different value :(
> > > >
> > > > Do you think there would be much work to do that ?
> > > > Do you think it would be a desired feature the knowledge of the best
> > > > value for each architecture with more precision ?
> > >
> > > Google for "dynticks". There's obviously an overhead associated with HZ
> > > not being a constant (the compiler cannot optimise many expressions),
> > > but the feature is being worked on nonetheless.
> >
> > Well Linus had the best idea in that thread (as usual) which was to
> > implement "dynamic ticks" by leaving HZ a constant, setting it to a high
> > value, and skipping ticks when idle. Has there been any work in that
> > direction?
>
> i did a bit of work in that area, but the stuff I came up with never
> seemed to work right, so I dropped it.
It's all still in development at the moment but not far from being available
again. We stood back a bit to make some structural changes before trying to
make it ready for prime time.
Cheers,
Con
next prev parent reply other threads:[~2005-10-28 4:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 23:18 The "best" value of HZ Claudio Scordino
2005-10-28 2:04 ` Luke Yang
2005-10-28 2:27 ` Randy.Dunlap
2005-10-28 2:31 ` Alistair John Strachan
2005-10-28 3:45 ` Lee Revell
2005-10-28 4:00 ` Jesper Juhl
2005-10-28 4:29 ` Con Kolivas [this message]
2005-10-28 21:29 ` Adrian Bunk
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=200510281429.39532.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=cloud.of.andor@gmail.com \
--cc=jesper.juhl@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=s0348365@sms.ed.ac.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