From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] HZ as a config option
Date: 05 Oct 2002 01:53:16 +0100 [thread overview]
Message-ID: <1033779196.1335.8.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <3D9E1BEA.7060804@us.ibm.com>
On Fri, 2002-10-04 at 23:53, Dave Hansen wrote:
> On large systems (like NUMA-Q, Intel Profusion, etc...), latency and
> user responsiveness become much less important. The extra scheduling
> overhead caused by higher HZ is bad.
>
> This is x86-only right now. Is there any wider desire to tune this at
> config time? Do any architecutures have strict rules as to what this
> can be set to?
You can't set this arbitarily, the NTP PLL's will only lock for certain
value ranges.
next prev parent reply other threads:[~2002-10-05 0:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-04 22:53 Dave Hansen
2002-10-05 0:53 ` Alan Cox [this message]
2002-10-07 16:58 ` Dave Hansen
2002-10-07 17:19 ` Alan Cox
2002-10-07 17:27 ` george anzinger
2002-10-07 19:27 ` Vojtech Pavlik
2002-10-07 20:25 ` george anzinger
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=1033779196.1335.8.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=haveblue@us.ibm.com \
--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®