From: David Brownell <david-b@pacbell.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: akpm@osdl.org, Alessandro Zummo <alessandro.zummo@towertech.it>,
linuxppc-dev@ozlabs.org, lethal@linux-sh.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ralf@linux-mips.org, Andi Kleen <ak@muc.de>,
paulus@samba.org, rmk@arm.linux.org.uk, davem@davemloft.net,
kkojima@rr.iij4u.or.jp
Subject: Re: NTP time sync
Date: Sat, 25 Nov 2006 15:22:18 -0800 [thread overview]
Message-ID: <200611251522.19900.david-b@pacbell.net> (raw)
In-Reply-To: <1164279605.5653.51.camel@localhost.localdomain>
On Thursday 23 November 2006 3:00 am, Benjamin Herrenschmidt wrote:
>
> 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.
Good point. Of course, one issue is that the NTP sync code all
seems to be platform-specific right now ... just like the code
to set the system time from an RTC at boot (except for the new
RTC framework stuff) and after resume.
- Dave
WARNING: multiple messages have this Message-ID (diff)
From: David Brownell <david-b@pacbell.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Andi Kleen <ak@muc.de>,
Alessandro Zummo <alessandro.zummo@towertech.it>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
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: Sat, 25 Nov 2006 15:22:18 -0800 [thread overview]
Message-ID: <200611251522.19900.david-b@pacbell.net> (raw)
In-Reply-To: <1164279605.5653.51.camel@localhost.localdomain>
On Thursday 23 November 2006 3:00 am, Benjamin Herrenschmidt wrote:
>
> 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.
Good point. Of course, one issue is that the NTP sync code all
seems to be platform-specific right now ... just like the code
to set the system time from an RTC at boot (except for the new
RTC framework stuff) and after resume.
- Dave
next prev parent reply other threads:[~2006-11-25 23:22 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
2006-11-23 11:00 ` Benjamin Herrenschmidt
2006-11-25 23:22 ` David Brownell [this message]
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=200611251522.19900.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=alessandro.zummo@towertech.it \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.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.