public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Cochran <richardcochran@gmail.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	John Stultz <john.stultz@linaro.org>,
	Arun Sharma <asharma@fb.com>, LKML <linux-kernel@vger.kernel.org>,
	Kumar Sundararajan <kumar@fb.com>
Subject: Re: clock_gettime_ns
Date: Wed, 11 Sep 2013 20:50:10 +0200	[thread overview]
Message-ID: <20130911185008.GB8759@netboy> (raw)
In-Reply-To: <CALCETrWJbtrC0FDKFQ7_qS8sdxd7LyJk562uAzrK1TJqy97YOA@mail.gmail.com>

On Mon, Sep 09, 2013 at 10:47:01AM -0700, Andy Lutomirski wrote:
> 
> 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.

I know Harlan Stenn of the Network Time Foundation is working on a new
timestamp API and presented a paper at the conference:

   Requirements for UTC and Civil Timekeeping on Earth
   A Colloquium Addressing a Continuous Time Standard
   University of Virginia, Charlottesville, May 29-31, 2013. 

   http://www.cacr.caltech.edu/futureofutc/

The slides are on that site, and I would bet that the paper could be
made available. In any case, since I think any kind of new time API idea
would benefit from review and acceptance from the NTP and BSD people.

Thanks,
Richard



  

  reply	other threads:[~2013-09-11 18:50 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             ` clock_gettime_ns H. Peter Anvin
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                 ` Richard Cochran [this message]
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=20130911185008.GB8759@netboy \
    --to=richardcochran@gmail.com \
    --cc=asharma@fb.com \
    --cc=hpa@zytor.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