[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20061122195153.GC22601@flint.arm.linux.org.uk>
Date: Wed, 22 Nov 2006 19:51:53 +0000
From: Russell King <rmk+lkml@....linux.org.uk>
To: Alessandro Zummo <alessandro.zummo@...ertech.it>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
David Brownell <david-b@...bell.net>, linuxppc-dev@...abs.org,
Kumar Gala <galak@...nel.crashing.org>,
Kim Phillips <kim.phillips@...escale.com>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Andi Kleen <ak@....de>, akpm@...l.org, davem@...emloft.net,
kkojima@...iij4u.or.jp, lethal@...ux-sh.org, paulus@...ba.org,
ralf@...ux-mips.org
Subject: Re: NTP time sync
On Wed, Nov 22, 2006 at 08:36:33PM +0100, Alessandro Zummo wrote:
>
>
> wrto the in-kernel NTP synchronization,
> as discussed before [1], my opinion
> is that it should be done in userland.
>
> Keeping it in kernel implies subtle code
> in each of the supported architectures.
>
> So, if the arch maintainers agree,
> I would suggest to schedule it for removal.
>
> [1] http://lkml.org/lkml/2006/3/28/358
Fine, provided there's also a shell tool that can enquire whether the
kernel is sync'd or not. (Currently the 11-minute update does not
occur when the kernel is desynced from a time source - the RTC itself
might be more accurate in this case.)
Throwing hwclock commands into crontab such that they do not take
note of the kernel's sync status is probably a very bad move in that
respect.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists