From: Hans Reiser <reiser@namesys.com>
To: Craig Soules <soules@happyplace.pdl.cmu.edu>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: NFS Client patch
Date: Wed, 18 Jul 2001 02:21:46 +0400 [thread overview]
Message-ID: <3B54BA7A.42B0E107@namesys.com> (raw)
In-Reply-To: <Pine.LNX.3.96L.1010717180713.13980K-100000@happyplace.pdl.cmu.edu>
Craig Soules wrote:
>
> On Wed, 18 Jul 2001, Hans Reiser wrote:
> > 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.....
>
> Unfortunately to comply with NFSv2, the cookie cannot be larger than
> 32-bits. I believe this oversight has been correct in later NFS versions.
>
> I do agree that forcing the underlying fs to "fix" itself for NFS is the
> wrong solution. I can understand their desire to follow unix semantics
> (although I don't entirely agree with them), so until I think up a more
> palatable solution for the linux community, I will just keep my patches to
> myself :)
>
> Craig
64 bits as in NFS v4 is still not large enough to hold a filename. For practical reasons, ReiserFS
does what is needed to work with NFS, but what is needed bad design features, and any FS designer
who doesn't feel the need to get along with NFS should not have acceptance of bad design be made a
criterion for the acceptance of his patches. Just let NFS not work for Craig's FS, what is the
problem with that?
Hans
next prev parent reply other threads:[~2001-07-17 22:23 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 [this message]
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
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=3B54BA7A.42B0E107@namesys.com \
--to=reiser@namesys.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--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