mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "jdow" <jdow@earthlink.net>
To: <root@chaos.analogic.com>, "Robert Love" <rml@tech9.net>
Cc: "Neil Conway" <nconway.list@ukaea.org.uk>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.4: variable HZ
Date: Sat, 19 Oct 2002 00:04:04 -0700	[thread overview]
Message-ID: <005601c2773d$b6fc65a0$6f1ee043@wizardess.wiz> (raw)
In-Reply-To: <Pine.LNX.3.95.1021018152117.150B-100000@chaos.analogic.com>

Richard, would you believe that this is essentially what is done with the
GPS satellites in the dither process and in the clock correction process
to make the drifty Rb standards as stable as ground standards?

(You'd better. I designed the beastie involved.)
{^_-}    Joanne, jdow@earthlink.net
----- Original Message ----- 
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: "Robert Love" <rml@tech9.net>
Cc: "Neil Conway" <nconway.list@ukaea.org.uk>; <linux-kernel@vger.kernel.org>
Sent: Friday, October 18, 2002 12:38
Subject: Re: [PATCH] 2.4: variable HZ


> On 18 Oct 2002, Robert Love wrote:
> 
> > On Fri, 2002-10-18 at 07:51, Neil Conway wrote:
> > 
> > > I was looking at your jiffies_to_clock_t() macro, and I notice that it
> > > will screw up badly if the user chooses a HZ value that isn't a multiple
> > > of the normal value (e.g. 1000 is OK, 512 isn't).
> > 
> > OK, sure, but why specify a power-of-two HZ?  There is absolutely no
> > reason to, at least on x86.
> > 
> > Want 512?  500 will do just as well and has the benefit of (a) being a
> > multiple of the previous HZ and (b) evenly dividing into our concept of
> > time.
> > 
> > Robert Love
> > 
> 
> At least on ix86, HZ needs to be something that CLOCK_TICK_RATE/LATCH
> comes out fairly close. Remember, LATCH is the divisor for the PIT
> and that PIT gets CLOCK_TICK_RATE for its input. If this number isn't
> fairly 'exact' there will be much jumping of time in the sawtooth
> corrector.
> 
> If you are not using ELAN, CLOCK_TICK_RATE is 1193180. If your HZ is
> 100, you have 1193180/100 = 1193.18, not too exact. 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.
> 
> Cheers,
> Dick Johnson
> Penguin : Linux version 2.4.18 on an i686 machine (797.90 BogoMips).
> The US military has given us many words, FUBAR, SNAFU, now ENRON.
> Yes, top management were graduates of West Point and Annapolis.
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2002-10-19  6:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-18 11:51 Neil Conway
2002-10-18 18:44 ` Robert Love
2002-10-18 19:38   ` Richard B. Johnson
2002-10-19  7:04     ` jdow [this message]
2002-10-21 13:13       ` Richard B. Johnson
2002-10-19  9:36     ` Willy Tarreau
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='005601c2773d$b6fc65a0$6f1ee043@wizardess.wiz' \
    --to=jdow@earthlink.net \
    --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

all inboxes | Powered by JetHome®