lkml.org 
[lkml]   [2013]   [Sep]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: clock_gettime_ns
On Wed, Sep 4, 2013 at 6:22 PM, H. Peter Anvin <hpa@zytor.com> wrote:
> I think it would be crazy encoding UTC with a non-POSIX scheme.

The whole point is to find a good way to return the time that solves
the problems with the POSIX scheme. Some of the problems, as I see
them, are:

- Performance: seconds + nanoseconds is expensive to compute and
expensive to use.
- Leap seconds, part 1: Times like 23:59:60.1 are not representable.
- Leap seconds, part 2: The limited leap-second support that already
exists (via the NTP APIs) is so obscure that it's frequently broken.
- Offsets between clocks can't be read without using complicated
calls like adjtimex.

I think that coming up with something that's both non-POSIX and
half-arsed is a bad idea, but doing something that's non-POSIX and
well thought-through could be valuable.

--Andy


\
 
 \ /
  Last update: 2013-09-09 20:01    [W:0.083 / U:0.052 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site