From: george anzinger <george@mvista.com>
To: davidm@hpl.hp.com
Cc: Andrew Morton <akpm@digeo.com>,
Richard C Bilson <rcbilson@plg2.math.uwaterloo.ca>,
linux-kernel@vger.kernel.org, Eric Piel <Eric.Piel@Bull.Net>,
Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
Subject: Re: setitimer 1 usec fails
Date: Tue, 27 May 2003 13:01:55 -0700 [thread overview]
Message-ID: <3ED3C433.6020002@mvista.com> (raw)
In-Reply-To: <16083.44589.855335.531141@napali.hpl.hp.com>
David Mosberger wrote:
>>>>>>On Mon, 26 May 2003 15:00:53 -0700, george anzinger <george@mvista.com> said:
>
>
> George> As a test, you might try your test with HZ=1000 (a number I
> George> recommend for ia64, if at all possible).
>
> I suspect you might have a slightly biased view on this. ;-) Yes,
> HZ=1000 makes some problems easier to convert ticks to real time, but
> slower to convert real time to ticks.
Ulrich has written something on this. Maybe he could comment :)
-g
>
> Besides, the Linux kernel MUST work with (fairly) arbitrary HZ values,
> because some platforms just don't have much of a choice (e.g., Alpha
> is pretty much forced to 1024Hz).
>
> But, yes, on ia64 we can choose HZ to our liking. If someone presents
> evidence that shows a real benefit for a value other than 1024, I'm
> certainly willing to listen.
>
> --david
>
>
--
George Anzinger george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml
next prev parent reply other threads:[~2003-05-27 19:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030526142555.67a79694.akpm@digeo.com>
2003-05-26 22:00 ` setitimer 1 usec fails george anzinger
2003-05-27 9:05 ` Eric Piel
2003-05-27 18:27 ` David Mosberger
2003-05-27 20:01 ` george anzinger [this message]
2003-05-27 17:19 Richard C Bilson
-- strict thread matches above, loose matches on Subject: below --
2003-05-26 21:09 Richard C Bilson
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=3ED3C433.6020002@mvista.com \
--to=george@mvista.com \
--cc=Eric.Piel@Bull.Net \
--cc=Ulrich.Windl@rz.uni-regensburg.de \
--cc=akpm@digeo.com \
--cc=davidm@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rcbilson@plg2.math.uwaterloo.ca \
/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.