From: Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: [PATCH 3/4] Add /proc/sys/fs/nfs sysctls to nfsd module
Date: Thu, 03 Aug 2006 13:08:00 -0400
Message-ID: <1154624881.5774.96.camel@localhost>
References: <20060803110538.GA17173@suse.de>
	<76bd70e30608030952p15e1500cy191b5ef19241b58e@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: Olaf Kirch <okir@suse.de>, nfs@lists.sourceforge.net
To: Chuck Lever <chucklever@gmail.com>
In-Reply-To: <76bd70e30608030952p15e1500cy191b5ef19241b58e@mail.gmail.com>
Sender: nfs-bounces@lists.sourceforge.net
Errors-To: nfs-bounces@lists.sourceforge.net

On Thu, 2006-08-03 at 09:52 -0700, Chuck Lever wrote:
> I don't recall the history of /proc/sys/fs -- is there also a
> /proc/sys/fs/nfsd directory, and wouldn't it be better to add this
> particular sysctl in there?

I too would prefer to reserve /proc/sys/fs/nfs for client and/or common
stuff (like the lockd listening ports).

There is an nfsd filesystem (usually mounted on /proc/fs/nfsd), for
which the above is more appropriate.

Note, however, that the entire sysctl should be unnecessary. Clients are
supposed to tell the server how large a reply to return, by means of the
'maxcount' argument (see RFC1813). If the clients aren't doing that,
then they really need to be fixed.
Linux clients should, AFAIK, always be setting maxcount to
PAGE_CACHE_SIZE == 4k.

Cheers,
  Trond


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs