From: David Newall <davidn@davidnewall.com>
To: Srinivas Nayak <sinu_nayak2001@yahoo.co.in>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BUG: Is it a bug in Linux time() function or Linux OS calls?
Date: Wed, 10 Mar 2010 19:17:48 +1030 [thread overview]
Message-ID: <4B975CB4.4000804@davidnewall.com> (raw)
In-Reply-To: <460422.78917.qm@web7603.mail.in.yahoo.com>
Dear Srinivas Nayak,
I don't suppose you're writing to a network mounted disk, with the
network device's clock about half a second behind your test machine?
Otherwise -- and I'm just guessing here, and will leave it to you to
UTSL -- this could be explained by use of two different algorithms for
converting a higher-resolution time source to the one-second
resolution. A truncation algorithm versus a rounding algorithm could
produce the result you demonstrate.
Regards,
David
next prev parent reply other threads:[~2010-03-10 8:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 7:59 BUG: Is it a bug in Linux time() function or Linux OS calls? Srinivas Nayak
2010-03-10 8:47 ` David Newall [this message]
2010-03-10 9:13 ` Srinivas Nayak
2010-03-10 17:19 ` john stultz
2010-03-11 6:10 ` Srinivas Nayak
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=4B975CB4.4000804@davidnewall.com \
--to=davidn@davidnewall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sinu_nayak2001@yahoo.co.in \
/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