From: Chris Mason <mason@suse.com>
To: Hans Reiser <reiser@namesys.com>, Andi Kleen <ak@suse.de>
Cc: Craig Soules <soules@happyplace.pdl.cmu.edu>,
linux-kernel@vger.kernel.org
Subject: Re: NFS Client patch
Date: Wed, 18 Jul 2001 09:57:56 -0400 [thread overview]
Message-ID: <177360000.995464676@tiny> (raw)
In-Reply-To: <3B54B5F9.8484715F@namesys.com>
On Wednesday, July 18, 2001 02:02:33 AM +0400 Hans Reiser <reiser@namesys.com> wrote:
> Andi Kleen wrote:
>>
>> Craig Soules <soules@happyplace.pdl.cmu.edu> writes:
>>
>> > Our system does automatic directory compaction through the use of a tree
>> > structure, and so the cookie needs to be invalidated. Also, any other
>> > file system whicih does immediate directory compaction would require this.
>>
>> Actually all the file systems who do that on Linux (JFS, XFS, reiserfs)
>> have fixed the issue properly server side, by adding a layer that generates
>> stable cookies. You should too.
>>
> I take issue with the word "properly". We have bastardized our FS design to do it. NFS should not
> be allowed to impose stable cookie maintenance on filesystems, it violates layering. Simply
> returning the last returned filename is so simple to code, much simpler than what we have to do to
> cope with cookies. Linux should fix the protocol for NFS, not ask Craig to screw over his FS
> design. Not that I think that will happen.....
>
Well, returning the last filename won't do much for filesystems that don't
have any directory indexes, but that's besides the point. Could nfsv4 be
better than it is? probably. Can we change older NFS protocols to have
a linux specific hack that makes them more filesystem (or at least reiserfs)
friendly? probably.
NFS is what it is, good and bad. People use it because it fits their setup
better than the others, so the filesystems need to cater to it, exactly
because it has such a large cross platform user base. Linux specific mods
take away from that cross platform base.
-chris
next prev parent reply other threads:[~2001-07-18 13:58 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.3.96L.1010709131315.16113O-200000@happyplace.pdl.cmu.edu.suse.lists.linux.kernel>
2001-07-09 18:33 ` NFS Client patch Andi Kleen
2001-07-10 13:33 ` Chris Wedgwood
2001-07-10 13:41 ` Andi Kleen
2001-07-10 16:48 ` Craig Soules
2001-07-10 17:06 ` Andi Kleen
2001-07-10 18:04 ` Chris Wedgwood
2001-07-12 20:57 ` Alan Cox
2001-07-13 11:26 ` Chris Wedgwood
2001-07-17 22:02 ` Hans Reiser
2001-07-17 22:14 ` Craig Soules
2001-07-17 22:21 ` Hans Reiser
2001-07-18 13:30 ` Daniel Phillips
2001-07-18 14:46 ` Hans Reiser
2001-07-18 14:00 ` Jan Harkes
2001-07-18 14:46 ` Hans Reiser
2001-07-19 18:24 ` Pavel Machek
2001-07-22 15:15 ` Rob Landley
2001-07-23 2:02 ` Horst von Brand
2001-07-23 9:57 ` Rob Landley
2001-07-18 13:57 ` Chris Mason [this message]
2001-07-19 11:35 ` Trond Myklebust
2001-07-19 18:02 ` Hans Reiser
2001-07-20 8:50 ` Trond Myklebust
2001-07-20 11:30 ` Hans Reiser
2001-07-20 14:07 ` Chris Mason
2001-07-09 17:28 Craig Soules
2001-07-09 18:59 ` Trond Myklebust
2001-07-09 19:45 ` Craig Soules
2001-07-09 19:53 ` Charles Cazabon
2001-07-09 20:05 ` Trond Myklebust
2001-07-09 22:09 ` Craig Soules
2001-07-10 8:22 ` Trond Myklebust
2001-07-10 13:38 ` Chris Wedgwood
2001-07-11 8:14 ` Trond Myklebust
2001-07-09 21:46 ` J. Richard Sladkey
2001-07-10 15:06 ` Craig Soules
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=177360000.995464676@tiny \
--to=mason@suse.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--cc=soules@happyplace.pdl.cmu.edu \
/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