public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: Robert Love <rml@tech9.net>,
	Neil Conway <nconway.list@ukaea.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.4: variable HZ
Date: Sat, 19 Oct 2002 11:36:10 +0200	[thread overview]
Message-ID: <20021019093610.GA16046@alpha.home.local> (raw)
In-Reply-To: <Pine.LNX.3.95.1021018152117.150B-100000@chaos.analogic.com>

On Fri, Oct 18, 2002 at 03:38:43PM -0400, Richard B. Johnson wrote:
> If you are not using ELAN, CLOCK_TICK_RATE is 1193180.

well, in fact it's 1193181.666... (14318180/12).

> If your HZ is 100, you have 1193180/100 = 1193.18, not too exact.

you meant 1000, I suppose ?

> if you use 500, you get 1193180/500 = 2386.36 which has twice as much
> round-off. If you use 1193180/512 = 2330.43, even a higher fractional
> part.

those interested can try 511 Hz (/2334.994) or 1900 Hz (/627.990) which
has the double advantage of being multiple of 100 Hz and have a little
drift due to frac part (/628 gives 1899.97 Hz, and /627 gives 1903.001 Hz).
If you don't need a multiple of 100 Hz, I noticed that dividing by 5709
gives 209.0001 Hz.

I'm also wondering why we never use the RTC as an interrupt source. Are
there any incompatible PCs ?

Cheers,
Willy


  parent reply	other threads:[~2002-10-19  9:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-18 11:51 [PATCH] 2.4: variable HZ Neil Conway
2002-10-18 18:44 ` Robert Love
2002-10-18 19:38   ` Richard B. Johnson
2002-10-19  7:04     ` jdow
2002-10-21 13:13       ` Richard B. Johnson
2002-10-19  9:36     ` Willy Tarreau [this message]
2002-10-21  8:15   ` Neil Conway
  -- strict thread matches above, loose matches on Subject: below --
2002-10-15  6:03 Robert Love
2002-10-15  6:50 ` Robert Love
2002-10-18 18:27 ` Tim Schmielau

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=20021019093610.GA16046@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nconway.list@ukaea.org.uk \
    --cc=rml@tech9.net \
    --cc=root@chaos.analogic.com \
    /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