From: Theodore Tso <tytso@mit.edu>
To: Cordenner jean noel <jean-noel.cordenner@bull.net>
Cc: Andreas Dilger <adilger@clusterfs.com>, linux-ext4@vger.kernel.org
Subject: Re: [RFC] [patch 2/3] change attribute for ext4: ext4 specific code
Date: Thu, 14 Dec 2006 11:03:07 -0500 [thread overview]
Message-ID: <20061214160307.GE9079@thunk.org> (raw)
In-Reply-To: <45803906.5070307@bull.net>
On Wed, Dec 13, 2006 at 06:31:50PM +0100, Cordenner jean noel wrote:
There was discussion on yesterday's call about whether or not 32-bit
was enough for NFSv4, or whether it also requried 64-bits of change
notification in the RFC's. So one of the questions is whether this is
something that would justify requiring 64-bits --- and if so, maybe we
need to require that big inodes be used and store the entire 64-bit
value beyond 128 bytes. This would mean that NFSv4 cache management
couldn't be fully implemented without big inodes, or we'd have to make
do by using the inode ctime as a partial substitute.
What do you think?
- Ted
next prev parent reply other threads:[~2006-12-14 16:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 18:54 [RFC] [patch 2/3] change attribute for ext4: ext4 specific code Jean-Noel Cordenner
2006-12-06 21:49 ` Andreas Dilger
2006-12-13 17:31 ` Cordenner jean noel
2006-12-14 16:03 ` Theodore Tso [this message]
2006-12-14 22:57 ` Andreas Dilger
2006-12-15 10:36 ` 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=20061214160307.GE9079@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@clusterfs.com \
--cc=jean-noel.cordenner@bull.net \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).