From: Arjan van de Ven <arjan@infradead.org>
To: Andrew Morton <akpm@osdl.org>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Work around for periodic do_gettimeofday hang
Date: Thu, 25 Nov 2004 09:20:53 +0100 [thread overview]
Message-ID: <1101370853.2659.1.camel@laptop.fenrus.org> (raw)
In-Reply-To: <20041124203349.7982efb7.akpm@osdl.org>
On Wed, 2004-11-24 at 20:33 -0800, Andrew Morton wrote:
> James Bottomley <James.Bottomley@SteelEye.com> wrote:
> >
> > +config X86_HZ
> > + int "Clock Tick Rate"
> > + default 1000 if !(M386 || M486 || M586 || M586TSC || M586MMX)
> > + default 100 if (M386 || M486 || M586 || M586TSC || M586MMX)
> > + help
> > + Select the kernel clock tick rate in interrupts per second.
> > + Slower processors should choose 100; everything else 1000.
>
> I guess we don't need the help, given that it's not a menuisable option.
> (There was a make-HZ-selectable patch once, and Linus spat it out).
I'd rather have it as menu-visible option, but I can see how arbitrary
HZ gets spat out. How about a radio-button like thing with "100" and
"1000" in it.
HZ=1000 costs you 1% HPC performance, and for slower machines probably more. Also some hw (with slow smm) really doesn't likeit.
next prev parent reply other threads:[~2004-11-25 9:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-24 16:49 James Bottomley
2004-11-24 19:13 ` Arjan van de Ven
2004-11-25 4:27 ` James Bottomley
2004-11-25 4:33 ` Andrew Morton
2004-11-25 4:40 ` James Bottomley
2004-11-25 8:20 ` Arjan van de Ven [this message]
2004-11-27 22:38 ` Lee Revell
2004-11-25 11:18 ` Roman Zippel
2004-11-25 13:42 ` Jan Engelhardt
2004-11-25 15:47 ` Alan Cox
2004-11-25 17:33 ` James Bottomley
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=1101370853.2659.1.camel@laptop.fenrus.org \
--to=arjan@infradead.org \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®