From: john stultz <johnstul@us.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Miroslav Lichvar <mlichvar@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: [GIT pull] ntp updates for 2.6.31
Date: Tue, 23 Jun 2009 14:41:56 -0700 [thread overview]
Message-ID: <1245793316.3305.5.camel@localhost> (raw)
In-Reply-To: <20090623133625.GA3026@elte.hu>
On Tue, 2009-06-23 at 15:36 +0200, Ingo Molnar wrote:
> The PPS patches i've seen just export IRQ timestamps to user-space.
>
> That is not very robust in my opinion when it comes to do time
> approximations - to get quick, low-latency action and precise
> measurements it's best to keep the critical path as short as
> possible, and within a single source code repository: i.e. within
> the kernel.
>
> There's little policy really, other than setting some general
> parameters. NTPd can still provide the raw _network time_
> timestamps, as that is probably best fetched by user-space and fed
> to the kernel.
At some point that stops being NTP. NTP has quite a bit of userland
policy for filtering and managing a number of different network clocks
(other ntp servers, PPS sources, etc).
>From what you're describing (direct offset from a hardware time device
used to steer the clock directly in kernel), you might want to look at
the STP code in s390 (stp_sync_clock).
thanks
-john
next prev parent reply other threads:[~2009-06-23 21:42 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
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 [this message]
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=1245793316.3305.5.camel@localhost \
--to=johnstul@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mlichvar@redhat.com \
--cc=schwidefsky@de.ibm.com \
--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 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.