linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean noel Cordenner <jean-noel.cordenner@bull.net>
To: linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	nfsv4@linux-nfs.org
Subject: [patch 0/2] i_version update
Date: Fri, 25 May 2007 18:25:31 +0200	[thread overview]
Message-ID: <46570DFB.3080101@bull.net> (raw)

Hi,

This is an update of the i_version patch.
The i_version field is a 64bit counter that is set on every inode
creation and that is incremented every time the inode data is modified
(similarly to the "ctime" time-stamp).
The aim is to fulfill a NFSv4 requirement for rfc3530:
"5.5.  Mandatory Attributes - Definitions
Name		#	DataType   Access   Description
___________________________________________________________________
change		3	uint64       READ     A value created by the
		server that the client can use to determine if file
		data, directory contents or attributes of the object
		have been modified.  The servermay return the object's
		time_metadata attribute for this attribute's value but
		only if the filesystem object can not be updated more
		frequently than the resolution of time_metadata.
"

The patch set is divided into 2parts, the vfs layer and a ext4 specific 
code.

Any comments welcome.

Cheers,
Jean noel

             reply	other threads:[~2007-05-25 16:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-25 16:25 Jean noel Cordenner [this message]
2007-05-30  0:21 ` [patch 0/2] i_version update David Chinner
2007-05-30 23:32   ` Mingming Cao
2007-05-31  0:33     ` David Chinner
2007-05-31 18:12       ` Mingming Cao
2007-05-31  0:01   ` Neil Brown
2007-05-31 12:36     ` Trond Myklebust

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=46570DFB.3080101@bull.net \
    --to=jean-noel.cordenner@bull.net \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@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).