From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: cmm@us.ibm.com
Cc: Andreas Dilger <adilger@clusterfs.com>,
jean-noel.cordenner@bull.net, linux-ext4@vger.kernel.org,
nfsv4@linux-nfs.org, linux-fsdevel@vger.kernel.org
Subject: Re: [patch 2/2] i_version update - ext4 part
Date: Wed, 30 May 2007 22:25:14 -0400 [thread overview]
Message-ID: <1180578314.6696.24.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <1180568925.3794.44.camel@dyn9047017103.beaverton.ibm.com>
On Wed, 2007-05-30 at 16:48 -0700, Mingming Cao wrote:
> On Tue, 2007-05-29 at 16:58 -0600, Andreas Dilger wrote:
> > I don't know what the NFS requirements for the version are. There may
> > also be some complaints from others if the i_version is 64 bits because
> > this contributes to generic inode growth and isn't used for other
> > filesystems.
> >
> That should benefit for other filesystems, as I thought this NFS
> requirements apply to all filesystems.
Right. The point here is that the NFS protocol needs to impose certain
requirements on _all_ filesystems that want to be supported, and so it
is in the interest of everyone to have a generic update mechanism
available in the VFS in order to avoid code (and bug) replication.
Now if Lustre doesn't care about NFS compatibility, then I suppose it
would be fairly easy to engineer the i_version update interface to allow
them to use that field in whatever way suits them best.
Trond
next prev parent reply other threads:[~2007-05-31 2:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-25 16:25 [patch 2/2] i_version update - ext4 part Jean noel Cordenner
2007-05-29 19:44 ` Mingming Cao
2007-05-29 22:58 ` Andreas Dilger
2007-05-30 23:48 ` Mingming Cao
2007-05-31 2:25 ` Trond Myklebust [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-05 15:28 [PATCH " Cordenner jean noel
2007-10-06 0:58 ` Mingming Cao
2007-10-25 17:04 ` Cordenner jean noel
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=1180578314.6696.24.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=adilger@clusterfs.com \
--cc=cmm@us.ibm.com \
--cc=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