lkml.org 
[lkml]   [2013]   [Sep]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: clock_gettime_ns
From
On Wed, Sep 4, 2013 at 11:51 AM, Andy Lutomirski <luto@amacapital.net> wrote:
> I think that most of the hangup was a lack of agreement on how the API
> should work wrt leap seconds.

I don't recall this objection. The interface uses existing clockids,
so it probably should keep the existing leap-second behavior of those
clockids.

> I've always thought that the Right Way to represent a UTC time is
> nanoseconds since some epoch, where every potential leap second
> counts.

Check out the CLOCK_TAI clockid merged in 3.10.

thanks
-john


\
 
 \ /
  Last update: 2013-09-04 21:41    [W:0.098 / U:0.856 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site