linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Staubach <staubach@redhat.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Andreas Dilger <adilger@clusterfs.com>,
	linux-ext4@vger.kernel.org, nfsv4@linux-nfs.org,
	Cordenner jean noel <jean-noel.cordenner@bull.net>
Subject: Re: [RFC] [patch 3/3] i_version update for ext4: user interface
Date: Wed, 24 Jan 2007 13:16:52 -0500	[thread overview]
Message-ID: <45B7A294.5030607@redhat.com> (raw)
In-Reply-To: <20070124181414.GC26806@fieldses.org>

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

      reply	other threads:[~2007-01-24 18:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-23 17:24 [RFC] [patch 3/3] i_version update for ext4: user interface Cordenner jean noel
2007-01-23 18:52 ` Andreas Dilger
2007-01-24 18:14   ` J. Bruce Fields
2007-01-24 18:16     ` Peter Staubach [this message]

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=45B7A294.5030607@redhat.com \
    --to=staubach@redhat.com \
    --cc=adilger@clusterfs.com \
    --cc=bfields@fieldses.org \
    --cc=jean-noel.cordenner@bull.net \
    --cc=linux-ext4@vger.kernel.org \
    --cc=nfsv4@linux-nfs.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;
as well as URLs for NNTP newsgroup(s).