From: Christoph Lameter <christoph@lameter.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Scalability enhancements for gettimeofday
Date: Tue, 08 Jun 2004 07:11:25 +0000 [thread overview]
Message-ID: <Pine.LNX.4.58.0406080008210.5817@server.home> (raw)
In-Reply-To: <200405201205.57930.clameter@sgi.com>
On Mon, 7 Jun 2004, David Mosberger wrote:
> Christoph> In this implementation get_offset can update "last_itc"
> Christoph> however many times wanted without any problem. last_itc
> Christoph> just insures that ITC becomes a monotonic clock like the
> Christoph> other clock sources. last_nsec_offset is not used and
> Christoph> could be removed.
>
> It doesn't matter what you're calling the variable. If you update a
> global variable with a bogus value, you lose. Sure, it will be
> monotonic, but if you get unlucky and the (bad) interpolated value
> jumped forward by a huge amount, you'll get horrible resolution for a
> long time to come.
How could this implementation put a bogus value into last_itc?
next prev parent reply other threads:[~2004-06-08 7:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-20 19:05 Scalability enhancements for gettimeofday Christoph Lameter
2004-06-02 17:33 ` David Mosberger
2004-06-02 20:58 ` John Hesterberg
2004-06-03 2:38 ` Jack Steiner
2004-06-03 4:56 ` Christoph Lameter
2004-06-03 16:28 ` Christoph Lameter
2004-06-03 20:04 ` Chris Wedgwood
2004-06-04 6:29 ` David Mosberger
2004-06-04 14:26 ` Christoph Lameter
2004-06-05 5:12 ` David Mosberger
2004-06-07 17:46 ` Christoph Lameter
2004-06-07 18:14 ` David Mosberger
2004-06-07 20:24 ` Christoph Lameter
2004-06-07 20:55 ` David Mosberger
2004-06-07 22:48 ` Christoph Lameter
2004-06-07 23:02 ` David Mosberger
2004-06-08 4:08 ` Christoph Lameter
2004-06-08 4:33 ` David Mosberger
2004-06-08 5:59 ` Christoph Lameter
2004-06-08 6:06 ` David Mosberger
2004-06-08 7:11 ` Christoph Lameter [this message]
2004-06-08 18:02 ` David Mosberger
2004-06-08 18:32 ` Christoph Lameter
2004-06-08 21:38 ` David Mosberger
2004-06-08 21:48 ` Christoph Lameter
2004-06-08 22:13 ` David Mosberger
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.0406080008210.5817@server.home \
--to=christoph@lameter.com \
--cc=linux-ia64@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