[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Linux 2.6 nanosecond time stamp weirdness breaks GCC build
From: |
James H. Cloos Jr. |
Subject: |
Re: Linux 2.6 nanosecond time stamp weirdness breaks GCC build |
Date: |
Fri, 02 Apr 2004 02:57:41 -0500 |
User-agent: |
Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3.50 (gnu/linux) |
>>>>> "Jamie" == Jamie Lokier <address@hidden> writes:
Jamie> When re-reading an inode, rounding the time up is done by
Jamie> setting the tv_nsec field to 999999999.
Jamie> If the on-disk timestamp is "now", i.e. the current second if
Jamie> it's a 1-second resolution, then we can avoid setting the
Jamie> timestamp to a future time by setting the tv_nsec field to the
Jamie> current wall time's nanosecond value. There is no need to
Jamie> round the time up any more than that.
Given how much time it will take to compare the file's timestamp to
current before choosing 999999999 or now for the tv_nsec field, is
it a reasonable shortcut to just always use now's nsec value?
Obviously it is not *that* many cycles to do the compare, but we are
talking about a nanoseconds field, and the current tv_sec could
increment during the compare....
-JimC
Re: Linux 2.6 nanosecond time stamp weirdness breaks GCC build,
James H. Cloos Jr. <=
Re: Linux 2.6 nanosecond time stamp weirdness breaks GCC build, Andrew Pimlott, 2004/04/03