public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Rodolfo Giometti <giometti@linux.it>
Cc: linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	David Woodhouse <dwmw2@infradead.org>,
	Dave Jones <davej@redhat.com>, Sam Ravnborg <sam@ravnborg.org>,
	Greg KH <greg@kroah.com>, Randy Dunlap <randy.dunlap@oracle.com>,
	Kay Sievers <kay.sievers@vrfy.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Michael Kerrisk <mtk.manpages@gmail.com>,
	Christoph Hellwig <hch@infradead.org>,
	John Stultz <johnstul@us.ibm.com>
Subject: Re: [PATCH 1/1] LinuxPPS core support.
Date: Sun, 22 Feb 2009 21:39:33 +0100	[thread overview]
Message-ID: <20090222203933.GA18914@elte.hu> (raw)
In-Reply-To: <1234274752-29847-2-git-send-email-giometti@linux.it>


* Rodolfo Giometti <giometti@linux.it> wrote:

> This patch adds the kernel side of the PPS support currently 
> named "LinuxPPS".
> 
> PPS means "pulse per second" and a PPS source is just a device 
> which provides a high precision signal each second so that an 
> application can use it to adjust system clock time.
> 
> Common use is the combination of the NTPD as userland program 
> with a GPS receiver as PPS source to obtain a wallclock-time 
> with sub-millisecond synchronisation to UTC.

Hm. I was looking at this stuff with the prospect of adding it 
to the timer tree, but i'm really struggling with a few 
fundamental questions.

The most basic one is: why do we need this?

The main purpose of your current patchset seems to be to deliver 
interrupt timestamps to user-space, where it will in essence be 
used to feed new adjtimex adjustments via ntpd.

I.e. the whole thing comes around in a circle in the end, but 
via user-space, where jitter will only increase.

Why not cut out the jittery middle man and add some intelligent 
API to register PPS interrupt sources straight with the NTP 
code, and let those IRQ timestamps be fed _directly_ into our 
time adjustment code?

	Ingo

  reply	other threads:[~2009-02-22 20:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-10 14:05 LinuxPPS core (Version 2): the PPS Linux implementation Rodolfo Giometti
2009-02-10 14:05 ` [PATCH 1/1] LinuxPPS core support Rodolfo Giometti
2009-02-22 20:39   ` Ingo Molnar [this message]
2009-02-22 20:57     ` H. Peter Anvin
2009-02-23  6:58       ` Ingo Molnar
2009-02-24 10:13         ` Rodolfo Giometti
2009-02-10 23:54 ` LinuxPPS core (Version 2): the PPS Linux implementation Andrew Morton
2009-02-10 23:58   ` H. Peter Anvin
2009-02-11  1:51     ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2009-05-22  6:12 LinuxPPS core (Version 3): " Rodolfo Giometti
2009-05-22  6:12 ` [PATCH 1/1] LinuxPPS core support Rodolfo Giometti
2009-05-26 23:33   ` Andrew Morton
2009-05-27  9:08     ` Alan Cox
2009-05-27 12:35       ` Folkert van Heusden
2009-05-27  9:38     ` Rodolfo Giometti
2009-02-01 17:55 LinuxPPS core (Version 1): the PPS Linux implementation Rodolfo Giometti
2009-02-01 17:55 ` [PATCH 1/1] LinuxPPS core support Rodolfo Giometti
2009-02-03  9:14   ` Christoph Hellwig

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=20090222203933.GA18914@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davej@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=giometti@linux.it \
    --cc=greg@kroah.com \
    --cc=hch@infradead.org \
    --cc=hpa@zytor.com \
    --cc=johnstul@us.ibm.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=randy.dunlap@oracle.com \
    --cc=sam@ravnborg.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