linux-kernel - Re: NTP time sync

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200611251522.19900.david-b@pacbell.net>
Date:	Sat, 25 Nov 2006 15:22:18 -0800
From:	David Brownell <david-b@...bell.net>
To:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
Cc:	Andi Kleen <ak@....de>,
	Alessandro Zummo <alessandro.zummo@...ertech.it>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linuxppc-dev@...abs.org, Kumar Gala <galak@...nel.crashing.org>,
	Kim Phillips <kim.phillips@...escale.com>, akpm@...l.org,
	davem@...emloft.net, kkojima@...iij4u.or.jp, lethal@...ux-sh.org,
	paulus@...ba.org, ralf@...ux-mips.org, rmk@....linux.org.uk
Subject: Re: NTP time sync

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

-
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/