From: "H. Peter Anvin" <hpa@zytor.com>
To: John Stultz <john.stultz@linaro.org>
Cc: Andy Lutomirski <luto@amacapital.net>,
Arun Sharma <asharma@fb.com>, LKML <linux-kernel@vger.kernel.org>,
Kumar Sundararajan <kumar@fb.com>
Subject: Re: clock_gettime_ns
Date: Wed, 04 Sep 2013 16:04:17 -0700 [thread overview]
Message-ID: <5227BC71.6000907@zytor.com> (raw)
In-Reply-To: <5227BB50.7000301@linaro.org>
On 09/04/2013 03:59 PM, John Stultz wrote:
>
> Also, there's been talk of a slewed-leap-second clockid, basically UTC
> but around the leapsecond it slows down to absorb the extra second. This
> means that clockid would have a subsecond offset from TAI.
>
Most of what I have heard seem to center around abolishing leap seconds
entirely. Now, I know that some users do slewed leap seconds as a
unofficial policy to avoid rare events.
-hpa
next prev parent reply other threads:[~2013-09-04 23:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 9:18 clock_gettime_ns Arun Sharma
2013-09-04 18:51 ` clock_gettime_ns Andy Lutomirski
2013-09-04 19:20 ` clock_gettime_ns John Stultz
2013-09-04 20:33 ` clock_gettime_ns Andy Lutomirski
2013-09-04 20:54 ` clock_gettime_ns John Stultz
2013-09-04 22:29 ` clock_gettime_ns H. Peter Anvin
2013-09-04 22:59 ` clock_gettime_ns John Stultz
2013-09-04 23:04 ` H. Peter Anvin [this message]
2013-09-04 23:20 ` clock_gettime_ns John Stultz
2013-09-04 23:38 ` clock_gettime_ns Andy Lutomirski
2013-09-05 1:22 ` clock_gettime_ns H. Peter Anvin
2013-09-09 17:47 ` clock_gettime_ns Andy Lutomirski
2013-09-11 18:50 ` clock_gettime_ns Richard Cochran
2013-09-04 19:17 ` clock_gettime_ns John Stultz
2013-09-04 20:23 ` clock_gettime_ns Andy Lutomirski
2013-09-04 20:50 ` clock_gettime_ns John Stultz
2013-09-05 4:45 ` clock_gettime_ns Arun Sharma
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5227BC71.6000907@zytor.com \
--to=hpa@zytor.com \
--cc=asharma@fb.com \
--cc=john.stultz@linaro.org \
--cc=kumar@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox