Re: [tip:timers/ntp] ntp: adjust SHIFT_PLL to improve NTP convergence

[Ingo Molnar <mingo@elte.hu>]

* John Stultz <johnstul@us.ibm.com> wrote:

> On Wed, 2009-05-06 at 09:46 +0000, tip-bot for john stultz wrote:
> > Commit-ID:  22cfbbfd9f67b67fe073010f51cb71d3632387d5
> > Gitweb:     http://git.kernel.org/tip/22cfbbfd9f67b67fe073010f51cb71d3632387d5
> > Author:     john stultz <johnstul@us.ibm.com>
> > AuthorDate: Wed, 6 May 2009 11:43:57 +0200
> > Committer:  Ingo Molnar <mingo@elte.hu>
> > CommitDate: Wed, 6 May 2009 11:44:02 +0200
> > 
> > ntp: adjust SHIFT_PLL to improve NTP convergence
> > 
> > The conversion to the ntpv4 reference model
> > f19923937321244e7dc334767eb4b67e0e3d5c74 ("ntp: convert to the NTP4
> > reference model") in 2.6.19 added nanosecond resolution the adjtimex
> > interface, but also changed the "stiffness" of the frequency adjustments,
> > causing NTP convergence time to greatly increase.
> > 
> > SHIFT_PLL, which reduces the stiffness of the freq adjustments, was
> > designed to be inversely linked to HZ, and the reference value of 4 was
> > designed for Unix systems using HZ=100.  However Linux's clock steering
> > code mostly independent of HZ.
> > 
> > So this patch reduces the SHIFT_PLL value from 4 to 2, which causes NTPd
> > behavior to match kernels prior to 2.6.19, greatly reducing convergence
> > times, and improving close synchronization through environmental thermal
> > changes.
> > 
> > The patch also changes some l's to L's in nearby code to avoid misreading
> > 50l as 501.
> > 
> > [ Impact: tweak NTP algorithm for faster convergence ]
> 
> Hey Ingo,
>
> 	So I've been speaking with Miroslav (cc'ed) who maintains 
> the RH ntpd packages, and he's concerned that this patch takes us 
> out of NTP's expected behavior, which may cause problems when 
> dealing with non-linux systems using NTP.

I might be missing something here - but Linux converging faster 
seems like a genuinely good thing. What non-Linux problem could 
there be? Linux's convergence is really Linux's private issue. 

(since things like the PIT calibration are random noise for which 
there can be no external expecation about our convergence speed 
anyway.)

	Ingo