[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALCETrUFLu1ekyaJFve4zARER7od-RyVy-JM+VsBBMgxvAFyoQ@mail.gmail.com>
Date: Fri, 23 Dec 2011 21:59:04 -0800
From: Andy Lutomirski <luto@...capital.net>
To: Richard Cochran <richardcochran@...il.com>
Cc: john stultz <johnstul@...ibm.com>, linux-kernel@...r.kernel.org,
Kumar Sundararajan <kumar@...com>,
Arun Sharma <asharma@...com>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...e.hu>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [RFC 0/2] ABI for clock_gettime_ns
On Thu, Dec 22, 2011 at 4:03 AM, Richard Cochran
<richardcochran@...il.com> wrote:
> On Wed, Dec 14, 2011 at 11:07:46AM -0800, john stultz wrote:
>> Maybe I'm still not understanding, but that seems more limited then what
>> is being proposed, at least in my mind. clock_gettime_ns() would still
>> take a clockid, so having a CLOCK_TAI would be a potential change in the
>> future.
>
> POSIX got the clock_gettime interface wrong, because you cannot tell
> the time with it. The POSIX interface will return the same time value
> for two consecutive seconds, due to leap seconds.
>
> IMHO, new interfaces should correct this mistake. So, a new interface
> providing UTC should also tell the user about leap seconds.
I agree. Hence the extra padding that can be used to fix this, once
the fix is available in core code.
I've written the patch and it's not as big an improvement as I hoped.
I'll play with it a bit and send it out soon.
--Andy
--
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/
Powered by blists - more mailing lists