From: Rik van Riel <riel@redhat.com>
To: John Stultz <johnstul@us.ibm.com>
Cc: Ingo Molnar <mingo@elte.hu>,
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: Mon, 01 Jun 2009 20:06:35 -0400 [thread overview]
Message-ID: <4A246D0B.40204@redhat.com> (raw)
In-Reply-To: <1243900716.11263.42.camel@jstultz-laptop>
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.
--
All rights reversed.
next prev parent reply other threads:[~2009-06-02 0:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 19:56 + ntp-adjust-shift_pll-to-improve-ntp-convergence.patch added to -mm tree akpm
2009-05-06 9:46 ` [tip:timers/ntp] ntp: adjust SHIFT_PLL to improve NTP convergence 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 [this message]
2009-06-02 0:20 ` Ingo Molnar
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=4A246D0B.40204@redhat.com \
--to=riel@redhat.com \
--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@elte.hu \
--cc=mingo@redhat.com \
--cc=mlichvar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.