From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andi Kleen <ak@muc.de>
Cc: akpm@osdl.org, Alessandro Zummo <alessandro.zummo@towertech.it>,
lethal@linux-sh.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ralf@linux-mips.org, David Brownell <david-b@pacbell.net>,
linuxppc-dev@ozlabs.org, paulus@samba.org, rmk@arm.linux.org.uk,
davem@davemloft.net, kkojima@rr.iij4u.or.jp
Subject: Re: NTP time sync
Date: Thu, 23 Nov 2006 22:00:05 +1100 [thread overview]
Message-ID: <1164279605.5653.51.camel@localhost.localdomain> (raw)
In-Reply-To: <20061123105400.GA75714@muc.de>
On Thu, 2006-11-23 at 11:54 +0100, Andi Kleen wrote:
> > [1] http://lkml.org/lkml/2006/3/28/358
>
> What was the answer to Matt's last question in there?
> If the existing user land does it already then
> probably. If not then a good migration strategy would
> be needed.
Couldn't we have a transition period by making the kernel not rely on
interrupts ? if the NTP irq code just triggers a work queue, then all of
a sudden, all of the RTC drivers can be used and the latency is small.
That might well be a good enough solution and is very simple.
Ben
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andi Kleen <ak@muc.de>
Cc: Alessandro Zummo <alessandro.zummo@towertech.it>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Brownell <david-b@pacbell.net>,
linuxppc-dev@ozlabs.org, Kumar Gala <galak@kernel.crashing.org>,
Kim Phillips <kim.phillips@freescale.com>,
akpm@osdl.org, davem@davemloft.net, kkojima@rr.iij4u.or.jp,
lethal@linux-sh.org, paulus@samba.org, ralf@linux-mips.org,
rmk@arm.linux.org.uk
Subject: Re: NTP time sync
Date: Thu, 23 Nov 2006 22:00:05 +1100 [thread overview]
Message-ID: <1164279605.5653.51.camel@localhost.localdomain> (raw)
In-Reply-To: <20061123105400.GA75714@muc.de>
On Thu, 2006-11-23 at 11:54 +0100, Andi Kleen wrote:
> > [1] http://lkml.org/lkml/2006/3/28/358
>
> What was the answer to Matt's last question in there?
> If the existing user land does it already then
> probably. If not then a good migration strategy would
> be needed.
Couldn't we have a transition period by making the kernel not rely on
interrupts ? if the NTP irq code just triggers a work queue, then all of
a sudden, all of the RTC drivers can be used and the latency is small.
That might well be a good enough solution and is very simple.
Ben
next prev parent reply other threads:[~2006-11-23 11:01 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 19:36 NTP time sync Alessandro Zummo
2006-11-22 19:36 ` Alessandro Zummo
2006-11-22 19:51 ` Russell King
2006-11-22 19:51 ` Russell King
2006-11-22 20:26 ` Alessandro Zummo
2006-11-22 20:26 ` Alessandro Zummo
2006-11-22 19:55 ` David Brownell
2006-11-22 19:55 ` David Brownell
2006-11-22 20:23 ` Alessandro Zummo
2006-11-22 20:23 ` Alessandro Zummo
2006-11-23 1:48 ` Gabriel Paubert
2006-11-23 1:48 ` Gabriel Paubert
2006-11-23 10:54 ` Andi Kleen
2006-11-23 10:54 ` Andi Kleen
2006-11-23 11:00 ` Benjamin Herrenschmidt [this message]
2006-11-23 11:00 ` Benjamin Herrenschmidt
2006-11-25 23:22 ` David Brownell
2006-11-25 23:22 ` David Brownell
2006-11-26 11:04 ` Joakim Tjernlund
2006-11-26 11:04 ` Joakim Tjernlund
2006-11-26 19:21 ` Alessandro Zummo
2006-11-26 19:21 ` Alessandro Zummo
2006-11-26 21:37 ` Joakim Tjernlund
2006-11-26 21:37 ` Joakim Tjernlund
2006-11-26 22:06 ` Michael Raskin
2006-11-26 22:53 ` Alessandro Zummo
2006-11-26 22:53 ` Alessandro Zummo
2006-11-27 1:21 ` [Bulk] " David Brownell
2006-11-27 1:21 ` David Brownell
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=1164279605.5653.51.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=alessandro.zummo@towertech.it \
--cc=davem@davemloft.net \
--cc=david-b@pacbell.net \
--cc=kkojima@rr.iij4u.or.jp \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=rmk@arm.linux.org.uk \
/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.