lkml.org 
[lkml]   [2011]   [Dec]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [RFC 0/2] ABI for clock_gettime_ns
    From
    Date
    On Wed, 2011-12-14 at 08:20 +0100, Richard Cochran wrote:
    > On Mon, Dec 12, 2011 at 07:43:02PM -0800, john stultz wrote:
    > >
    > > Having a CLOCK_TAI would be interesting across the board. We already
    > > keep a TAI offset in the ntp code. However, I'm not sure if ntp actually
    > > sets it these days.
    >
    > A bit OT, but what do think of the idea of keeping TAI in the kernel,
    > and providing UTC via a tabular conversion routine?

    Agreed its OT for this thread.

    > Michel Hack wrote an article last year detailing how Linux botches the
    > leap second and suggested a more robust way to handle it.

    Hmm. Do you have a link to the article?

    I like the idea of having TAI as a kernel clockid. The hard part is
    getting systems to initialize it properly at boot.

    Also part of the issue with leapseconds is that time functions are such
    a hot path, we can't really add extra conditionals checking for leap
    seconds. Instead the leapsecond occurs on the first tick of the
    leapsecond.

    More interestingly to me is Google's recent use of slewed leapseconds.
    However, how that would work on a public network is a bit more fuzzy.
    And being able to support both TAI and slewed leapseconds would require
    quite a bit more logic.

    thanks
    -john




    \
     
     \ /
      Last update: 2011-12-14 17:29    [W:2.554 / U:0.032 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site