From: Christoph Lameter <clameter@sgi.com>
To: George Anzinger <george@mvista.com>
Cc: john stultz <johnstul@us.ibm.com>,
lkml <linux-kernel@vger.kernel.org>,
ia64 <linux-ia64@vger.kernel.org>
Subject: Re: gettimeofday nanoseconds patch (makes it possible for the posix-timer functions to return higher accuracy)
Date: Thu, 15 Jul 2004 19:44:13 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0407151941010.24953@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <40F70C6D.5050506@mvista.com>
On Thu, 15 Jul 2004, George Anzinger wrote:
> As to accuracy, the more "accurate" way is to change get_offset to return
> nanoseconds. This way there is only one round off (by the divide) instead of
> two (the get_offset and the divide). I ran into this problem in the latest HRT
> patch. One of my tests is to do a gettimeofday and a clock_gettime and make
> sure there is no "backward" stuff happening. Test failed by 1 micro second
> "some" of the time because of this double round off.
Well yes this is what the interpolator etc does on IA64.
time_interpolator_get_offset returns nanoseconds. I have done
tests to insure that no backward stuff happens. Tests were done
with the mentioned patch and clock_gettime was returning nanosecond
accuracy.
next prev parent reply other threads:[~2004-07-16 2:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-14 16:41 Christoph Lameter
2004-07-14 20:09 ` john stultz
2004-07-14 20:28 ` Christoph Lameter
2004-07-14 21:14 ` David Mosberger
2004-07-14 21:15 ` john stultz
2004-07-15 0:08 ` Christoph Lameter
2004-07-15 0:48 ` john stultz
2004-07-15 1:16 ` David Mosberger
2004-07-15 1:35 ` john stultz
2004-07-15 3:57 ` David Mosberger
2004-07-15 15:31 ` Christoph Lameter
2004-07-15 16:14 ` john stultz
2004-07-15 17:03 ` Christoph Lameter
2004-07-15 17:18 ` john stultz
2004-07-15 22:59 ` George Anzinger
2004-07-16 2:44 ` Christoph Lameter [this message]
2004-07-14 21:09 ` Matthew Wilcox
2004-07-14 21:27 ` Christoph Lameter
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=Pine.LNX.4.58.0407151941010.24953@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=george@mvista.com \
--cc=johnstul@us.ibm.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®