From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Kuwahara,T." <6vvetjsrt26xsrzlh1z0zn4d2grdah-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> Subject: Re: [PATCH V8 02/13] ntp: add ADJ_SETOFFSET mode bit Date: Mon, 10 Jan 2011 06:07:26 +0900 Message-ID: References: <20110108175028.GA22308@riccoc20.at.omicron.at> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: <20110108175028.GA22308-7KxsofuKt4IfAd9E5cN8NEzG7cXyKsk/@public.gmane.org> Sender: linux-api-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Richard Cochran Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Alan Cox , Arnd Bergmann , Christoph Lameter , David Miller , John Stultz , Krzysztof Halasa , Peter Zijlstra , Rodolfo Giometti , Thomas Gleixner List-Id: linux-api@vger.kernel.org On Sun, Jan 9, 2011 at 2:50 AM, Richard Cochran wrote: > we want to be able to jump the clock arbitrarily. Another problem remains: How do you deal with leap seconds? I mean, given that 1 minute is not always 60 seconds, then what time was it XXXXX seconds ago? Maybe some kind of lookup table is necessary, but in such case, isn't it a better choice just to use the clock_settime/settimeofday syscall?