From: Christoph Lameter <christoph@lameter.com>
To: linux-ia64@vger.kernel.org
Subject: Re: time to reconsider HZ?
Date: Wed, 19 Jan 2005 16:54:09 +0000 [thread overview]
Message-ID: <Pine.LNX.4.58.0501190852300.26378@server.graphe.net> (raw)
In-Reply-To: <16872.45685.696721.811934@napali.hpl.hp.com>
On Fri, 14 Jan 2005, David Mosberger wrote:
> Since most other Linux platforms which use HZ>100 use a HZ value of
> 1000, I'm thinking it may be safer to switch ia64 to HZ\x1000 as well
> (principle of least difference possible is generally a good one...).
>
> In the past, I was concerned that there might be enough code that
> divides by HZ that this might not be such a hot idea, but I think this
> may not (or at least no longer) be the case: I compiled the same
> kernel once with HZ\x1000 and once with HZ\x1024 and the code-size
> actually shrunk.
>
> What do others think?
I think its not a big issue and may still be beneficial if occasions arise
where one has to divide by HZ. Do you know why the code size is reduced?
next prev parent reply other threads:[~2005-01-19 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-15 6:04 time to reconsider HZ? David Mosberger
2005-01-19 16:54 ` Christoph Lameter [this message]
2005-01-19 17:40 ` David Mosberger
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=Pine.LNX.4.58.0501190852300.26378@server.graphe.net \
--to=christoph@lameter.com \
--cc=linux-ia64@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