From: Andi Kleen <ak@suse.de>
To: Paul Eggert <eggert@twinsun.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: nanosecond file timestamp resolution in filesystems, GNU make, etc.
Date: 28 Oct 2002 12:05:49 +0100 [thread overview]
Message-ID: <p73u1j6su0i.fsf@oldwotan.suse.de> (raw)
In-Reply-To: Paul Eggert's message of "28 Oct 2002 10:55:39 +0100"
Paul Eggert <eggert@twinsun.com> writes:
>
> > Another way would be to round on flush, but that also has some problems :-
>
> Rounding is even worse. GNU Make assumes truncation, i.e. it assumes
> that a timestamp is truncated (floored, actually) when it is stored on
> a non-nanosecond-aware filesystem.
That is what my patchkit does currently, so I guess it should work fine.
>
> > In my current patchkit I just chose to truncate because that was the
> > easiest and the other more complicated solutions didn't offer any
> > compeling advantage.
>
> Can't you truncate/floor to filesystem timestamp resolution
> immediately, i.e., before the inode is flushed? That would address
> the problems that I see.
That would complicate the timestamp management in the kernel considerably.
I'm not sure if I want to do that, probably not.
-Andi
next parent reply other threads:[~2002-10-28 10:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20021027153651.GB26297@pimlott.net.suse.lists.linux.kernel>
[not found] ` <200210280947.g9S9l9H01162@sic.twinsun.com.suse.lists.linux.kernel>
2002-10-28 11:05 ` Andi Kleen [this message]
[not found] ` <20021028102809.GA16062@bjl1.asuk.net.suse.lists.linux.kernel>
2002-10-28 11:08 ` Andi Kleen
2002-10-28 12:56 ` Jamie Lokier
2002-10-28 14:15 ` Andi Kleen
2002-10-28 14:28 ` Maciej W. Rozycki
2002-10-28 15:13 ` Jamie Lokier
2002-10-28 15:40 ` Maciej W. Rozycki
2002-10-28 15:59 ` Jamie Lokier
2002-10-28 15:17 ` Jamie Lokier
[not found] <20021027153651.GB26297@pimlott.net>
2002-10-28 9:47 ` Paul Eggert
2002-10-28 10:28 ` Jamie Lokier
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=p73u1j6su0i.fsf@oldwotan.suse.de \
--to=ak@suse.de \
--cc=eggert@twinsun.com \
--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®