From: Ville Herva <vherva@niksula.hut.fi>
To: Robert Love <rml@tech9.net>
Cc: Cort Dougan <cort@fsmlabs.com>, linux-kernel@vger.kernel.org
Subject: Re: [STATUS 2.5] July 10, 2002
Date: Wed, 10 Jul 2002 23:41:56 +0300 [thread overview]
Message-ID: <20020710204156.GH1465@niksula.cs.hut.fi> (raw)
In-Reply-To: <1026332738.1244.86.camel@sinai>
On Wed, Jul 10, 2002 at 01:25:38PM -0700, you [Robert Love] wrote:
> On Wed, 2002-07-10 at 13:20, Cort Dougan wrote:
>
> > Why was the rate incremented to maintain interactive performance? Wasn't
> > that the whole idea of the pre-empt work? Does the burden of pre-empt
> > actually require this?
>
> I did not say it was increased to improve interactivity response - and
> it certainly has little or nothing to do with kernel preemption being
> merged.
>
> I suspect a big benefit would be poll/select performance. I think this
> is why RedHat increased HZ in their kernels.
Red Hat Limbo ChangeLog says:
"The kernel used in this release supports the following list of improvements
and new features. The kernel is based on the 2.4.19- pre10-ac2 release for
this beta."
"HZ=1000 on i686 and Athlon means that the system clock ticks 10 times as
fast as on other x86 platforms (i386 and i586); HZ=100 has been the Linux
default on x86 platforms for the entire history of the Linux kernel. This
change provides better interactive response, lower latency response from
some programs, and better response from the scheduler. We have adjusted the
/proc filesystem to report numbers as if using the default HZ=100, but it is
possible that issues could arise -- please test and report bugs, as always."
So they aim for interactive response. Otoh, I think they don't include
pre-emp nor any low-lat work. I might be wrong. But the network console and
crash dump functionality they include (by Ingo Molner, I reckon) seems
sweet.
-- v --
v@iki.fi
next prev parent reply other threads:[~2002-07-10 20:39 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-10 5:11 [STATUS 2.5] July 10, 2002 Guillaume Boissiere
2002-07-10 15:49 ` Rik van Riel
2002-07-10 16:19 ` Adrian Bunk
2002-07-10 16:31 ` Thunder from the hill
2002-07-10 16:51 ` Roman Zippel
2002-07-10 17:00 ` Thunder from the hill
2002-07-10 16:54 ` Karim Yaghmour
2002-07-10 17:25 ` John Levon
2002-07-10 19:19 ` Karim Yaghmour
2002-07-10 17:17 ` Alan Cox
2002-07-10 20:21 ` Daniel Phillips
2002-07-10 17:12 ` Patrick Mochel
2002-07-10 17:42 ` Arnaldo Carvalho de Melo
2002-07-10 17:54 ` Robert Love
2002-07-10 19:18 ` Ville Herva
2002-07-10 20:03 ` Robert Love
2002-07-10 20:20 ` Cort Dougan
2002-07-10 20:25 ` Robert Love
2002-07-10 20:41 ` Ville Herva [this message]
2002-07-10 21:07 ` Alan Cox
2002-07-10 20:46 ` Robert Love
2002-07-11 9:46 ` Rogier Wolff
2002-07-10 20:26 ` Justin M. Forbes
2002-07-10 17:46 Perches, Joe
2002-07-10 18:05 ` Thunder from the hill
2002-07-10 18:38 ` Alan Cox
2002-07-10 18:49 ` Kurt Garloff
2002-07-10 19:19 ` Larry Kessler
2002-07-10 21:15 ` Alan Cox
2002-07-11 18:07 ` Anton Blanchard
2002-07-10 21:27 ` Alan Cox
2002-07-10 18:08 Russ Weight
2002-07-11 19:21 Richard J Moore
2002-07-11 20:34 Richard J Moore
2002-07-13 9:28 ` Ingo Oeser
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=20020710204156.GH1465@niksula.cs.hut.fi \
--to=vherva@niksula.hut.fi \
--cc=cort@fsmlabs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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.