From: Ingo Molnar <mingo@elte.hu>
To: Rik van Riel <riel@redhat.com>
Cc: John Stultz <johnstul@us.ibm.com>,
mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, tglx@linutronix.de,
linux-tip-commits@vger.kernel.org,
Miroslav Lichvar <mlichvar@redhat.com>
Subject: Re: [tip:timers/ntp] ntp: adjust SHIFT_PLL to improve NTP convergence
Date: Tue, 2 Jun 2009 02:20:39 +0200 [thread overview]
Message-ID: <20090602002039.GA16410@elte.hu> (raw)
In-Reply-To: <4A246D0B.40204@redhat.com>
* Rik van Riel <riel@redhat.com> wrote:
> John Stultz wrote:
>> On Tue, 2009-06-02 at 01:22 +0200, Ingo Molnar wrote:
>
>>> 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.
>>
>> Yea. It does seem that way. Miroslav can likely expand on the
>> issue to help clarify, but as I understand it, the example is if
>> you have a number of systems that are peers in an NTP network.
>> All of them are using the same userland NTP daemon. However, if
>> the rate of change that corrections are applied is different in
>> half of them, you will have problems getting all the systems to
>> converge together.
>
> Would this not be true already, because the convergence of Linux
> system suddenly became a lot slower in 2.6.19?
>
> Damned if we do, damned if we don't - except the new behaviour
> introduced by your patches is nicer.
Not just that - but there's calibration noise during bootup that can
cause randomly distributed recalibrations as well. So other hosts in
a mixed environment will see inconsistencies anyway, after every
bootup.
NTP is all about being able to be resilient against time noise and
being able to sync up to a common time base ASAP.
Ingo
next prev parent reply other threads:[~2009-06-02 0:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200905051956.n45JuVo9025575@imap1.linux-foundation.org>
2009-05-06 9:46 ` tip-bot for john stultz
2009-05-12 1:13 ` john stultz
2009-05-12 9:31 ` [tip:timers/ntp] ntp: fix comment typos tip-bot for john stultz
2009-05-28 20:33 ` [tip:timers/ntp] ntp: adjust SHIFT_PLL to improve NTP convergence John Stultz
2009-06-01 23:22 ` Ingo Molnar
2009-06-01 23:58 ` John Stultz
2009-06-02 0:06 ` Rik van Riel
2009-06-02 0:20 ` Ingo Molnar [this message]
2009-06-02 16:22 ` Miroslav Lichvar
2009-06-02 20:55 ` john stultz
2009-06-02 0:29 ` John Stultz
2009-06-02 3:39 ` Ray Lee
2009-06-02 17:47 ` Mr. James W. Laferriere
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=20090602002039.GA16410@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mlichvar@redhat.com \
--cc=riel@redhat.com \
--cc=tglx@linutronix.de \
/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®