From: John Stultz <johnstul@us.ibm.com>
To: George Spelvin <linux@horizon.com>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de,
ulrich.windl@rz.uni-regensburg.de, williams@redhat.com,
zippel@linux-m68k.org
Subject: Re: [RFC][PATCH] Adjust SHIFT_PLL to improve NTP convergence.
Date: Wed, 06 May 2009 08:44:00 -0700 [thread overview]
Message-ID: <1241624640.9110.3.camel@jstultz-laptop> (raw)
In-Reply-To: <20090506144645.30215.qmail@science.horizon.com>
On Wed, 2009-05-06 at 10:46 -0400, George Spelvin wrote:
> > As always, feedback or testing (especially on non-x86 arches) would be
> > greatly appreciated.
>
> Applying it to a couple of PPS-synchronized machines (where I had already
> dropped the poll interval into the basement for better convergence, have
> to try reverting that) seems to be working.
Thanks for the testing!
> One thing I just noticed, although I'm sure it has happened in the past,
> is that there's a frequency jump each boot due to TSC recalibration.
>
> Machine 1 Machine 2
> Old CPU MHz 2500.170 2500.138
> Old NTP ppm -24.63 +/-0.01 -30.27 +/-0.02
>
> New CPU MHz 2500.176 2500.193
> New NTP ppm -22.26 +/-0.01 -8.20 +/-0.015
>
> "True" CPU MHz 2500.2316 2500.2136
>
> I should look and see if there's an easy way to tighten that tolerance.
> The current algorithm is fine for jiffies purposes, but a few seconds'
> worth of background calibration would produce a more stable estimate.
Yea. The TSC calibration issue has been around for awhile. Although the
code has been tweaked recently, I'm not seeing that much improved
consistency from reboot to reboot.
Its a hard trade off for folks who need very quick boot time, vs folks
that want very stable and accurate clocks across reboots.
I'll be looking into the calibration code to see how much is needed to
bring the error rate down.
thanks
-john
next prev parent reply other threads:[~2009-05-06 15:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-04 21:03 [RFC][PATCH] Adjust SHIFT_PLL to improve NTP convergence john stultz
2009-05-05 0:27 ` Rik van Riel
2009-05-06 14:46 ` George Spelvin
2009-05-06 15:44 ` John Stultz [this message]
2009-05-07 6:07 ` George Spelvin
2009-05-07 9:14 ` Ulrich Windl
2009-05-07 18:07 ` George Spelvin
2009-05-07 19:37 ` john stultz
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=1241624640.9110.3.camel@jstultz-laptop \
--to=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@horizon.com \
--cc=tglx@linutronix.de \
--cc=ulrich.windl@rz.uni-regensburg.de \
--cc=williams@redhat.com \
--cc=zippel@linux-m68k.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