[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <45B7A294.5030607@redhat.com>
Date: Wed, 24 Jan 2007 13:16:52 -0500
From: Peter Staubach <staubach@...hat.com>
To: "J. Bruce Fields" <bfields@...ldses.org>
CC: Andreas Dilger <adilger@...sterfs.com>, linux-ext4@...r.kernel.org,
nfsv4@...ux-nfs.org,
Cordenner jean noel <jean-noel.cordenner@...l.net>
Subject: Re: [RFC] [patch 3/3] i_version update for ext4: user interface
J. Bruce Fields wrote:
> On Tue, Jan 23, 2007 at 11:52:08AM -0700, Andreas Dilger wrote:
>
>> On Jan 23, 2007 18:24 +0100, Cordenner jean noel wrote:
>>
>>> This patch adds a ``st_i_version'' field in the stat
>>> structure, and modifies the stat(2) syscall accordingly. Currently the
>>> change is only visible on i386 and x86_64 archs.
>>>
>> What is the need for exporting i_version to userspace?
>>
>
> Maybe none, but it seems potentially really useful to me; in practice
> aren't most uses of mtime/ctime exactly in order to find out if the file
> has changed recently?
>
> Who else is asking for finer time resolutions? Is it because they need
> the precision (or the inter-file comparison) or because they need to
> know whether a file has changed?
>
> Isn't anybody that currently maintains some cached information about a
> filesystem currently living with the same races as NFS?
Doesn't the BSD stat struct have a field like this? If so, perhaps
they can remember why it was deemed to be interesting?
Thanx...
ps
-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists