Re: [GIT pull] ntp updates for 2.6.31

[Ingo Molnar]

* Miroslav Lichvar <mlichvar@xxxxxxxxxx> wrote:

> On Wed, Jun 17, 2009 at 07:26:01PM +0200, Ingo Molnar wrote:
> > * Miroslav Lichvar <mlichvar@xxxxxxxxxx> wrote:
> > 
> > > Still, I'd really like to see the original behavior restored. 
> > > Most of the users complaining about slow convergence are 
> > > probably just hitting the calibration problem, which needs to 
> > > be fixed by other means than making PLL faster. Also, users of 
> > > other systems seem to be happy with their slow convergence. At 
> > > least that's the impression I have from NTP lists.
> > 
> > Wouldnt the goal be to calibrate as fast as possible? (Without 
> > any bad oscillation)
> 
> Not really. It depends on how noisy is the input signal. On an 
> idle LAN the jitter is just few microseconds, but over internet it 
> easily reaches miliseconds. Over a certain point faster PLL will 
> just make things worse.

That is what i called 'bad oscillation' - a 'too fast' PLL that 
over-compensates and does not converge well enough.

Is there a claim that this change causes that? (John's testing 
suggested that there's no such effect)

> PLL is mainly about handling the signal noise, frequency adjusting 
> is secondary. When the noise is very low or the update interval is 
> long enough, the frequency variations caused by temperature 
> changes will dominate the signal noise and this is where FLL 
> should kick in.
> 
> The PLL/FLL switching is controlled by update interval. Ideally it 
> would be adaptive, but NTP is not that sophisticated. By default, 
> FLL is enabled when the interval is longer than 2048 seconds. This 
> is of course not the optimal value for all systems.
> 
> Unfortunately in kernel it can be configured only to 2048 or 256 
> and NTP never uses the shorter one. The NTP daemon has its own 
> loop which can be used instead and it allows to use arbitrary 
> values though.

How about going towards the ideal, adaptive design, to which ntpd 
passes in time samples and which observes noise and converges as 
quickly as possible (given the noise level) and stays stable once 
there? I guess we need extensions to the NTP syscall for that.

The NTP code in kernel/time/ntp.c is now reasonably clean for 
efforts like that.

It would also pave the way to properly support PPS devices in the 
kernel. Would you be interested in things like this?

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/