From: Miroslav Lichvar <mlichvar@redhat.com>
To: John Stultz <johnstul@us.ibm.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT pull] ntp updates for 2.6.31
Date: Wed, 17 Jun 2009 19:23:25 +0200 [thread overview]
Message-ID: <20090617172325.GA32332@localhost> (raw)
In-Reply-To: <1245253102.6067.94.camel@jstultz-laptop>
On Wed, Jun 17, 2009 at 08:38:22AM -0700, John Stultz wrote:
> On Tue, 2009-06-16 at 14:52 +0200, Miroslav Lichvar wrote:
> > If Linux really needs to have the fastest PLL, could it be done by
> > modifying the time constant passed in adjtimex structure instead of
> > changing SHIFT_PLL? The PLL response will be exactly the same, but it
> > will allow the applications (and admins) to detect that it is
> > different than expected.
> >
> > Something like:
> >
> > --- a/kernel/time/ntp.c
> > +++ b/kernel/time/ntp.c
> > @@ -425,6 +425,8 @@
> > time_constant = txc->constant;
> > if (!(time_status & STA_NANO))
> > time_constant += 4;
> > + /* We want faster PLL */
> > + time_constant -= 2;
> > time_constant = min(time_constant, (long)MAXTC);
> > time_constant = max(time_constant, 0l);
> > }
>
>
> It looks mathematically equivalent, although I've not had time to test
> it yet. Probably needs a bigger comment :)
>
> The nice thing with this version is that we're able to expose that the
> behavior would be different then other systems, but the other side of
> that coin might be that when the user specifies a time_constant value,
> the interface will show a different one being used. This might cause
> some bug reports saying the interface isn't responding properly, or
> something. Although this is already the case for !STA_NANO, and so far
> few have noticed.
I have checked the NTP sources and the returned time constant is used
only for reporting, at least for NTP it shouldn't cause any problems.
Returning correct time constant will be very useful if NTP developers
decide to use lower values or have it configurable as decreasing the
constant by another two will make the PLL unstable.
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.
Thanks,
--
Miroslav Lichvar
next prev parent reply other threads:[~2009-06-17 17:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 14:06 [GIT pull] ntp updates for 2.6.31 Thomas Gleixner
2009-06-15 20:16 ` john stultz
2009-06-15 23:41 ` john stultz
2009-06-16 9:06 ` Ingo Molnar
2009-06-16 11:29 ` Thomas Gleixner
2009-06-16 12:52 ` Miroslav Lichvar
2009-06-17 15:38 ` John Stultz
2009-06-17 16:51 ` Ingo Molnar
2009-06-17 17:23 ` Miroslav Lichvar [this message]
2009-06-17 17:26 ` Ingo Molnar
2009-06-17 17:55 ` John Stultz
2009-06-18 12:13 ` Miroslav Lichvar
2009-06-23 9:57 ` Ingo Molnar
2009-06-23 13:16 ` Miroslav Lichvar
2009-06-23 13:36 ` Ingo Molnar
2009-06-23 14:33 ` Miroslav Lichvar
2009-06-23 19:18 ` Ingo Molnar
2009-06-23 19:49 ` Miroslav Lichvar
2009-06-23 21:41 ` john stultz
2009-06-24 9:29 ` Alan Cox
2009-06-24 13:39 ` Martin Schwidefsky
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=20090617172325.GA32332@localhost \
--to=mlichvar@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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