From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Greg Banks <gnb@melbourne.sgi.com>
Cc: Olaf Kirch <okir@suse.de>,
Linux NFS Mailing List <nfs@lists.sourceforge.net>,
Chuck Lever <chucklever@gmail.com>
Subject: Re: [PATCH 3/4] Add /proc/sys/fs/nfs sysctls to nfsd module
Date: Fri, 04 Aug 2006 11:36:37 -0400 [thread overview]
Message-ID: <1154705797.4727.18.camel@localhost> (raw)
In-Reply-To: <1154680981.21040.2415.camel@hole.melbourne.sgi.com>
On Fri, 2006-08-04 at 18:43 +1000, Greg Banks wrote:
> On Fri, 2006-08-04 at 02:52, Chuck Lever wrote:
> > On 8/3/06, Olaf Kirch <okir@suse.de> wrote:
> > > From: okir@suse.de
> > > Subject: Add /proc/sys/fs/nfs sysctls to nfsd module
> > >
> > > This patch adds the plumbing for adding nfs-specific sysctls to fs/nfs,
> > > and makes the max size of a readdirplus reply tunable.
> > >
> > > The reason for this is that we found that some clients do not seem
> > > to grok readdirplus replies larger than 4K. Rather than reducing the
> > > overall number this sysctl allows admins to work around these clients.
>
> Neat.
Not really. It would be better to identify and fix the buggy clients
that aren't setting the READDIRPLUS maxcount parameter correctly.
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
next prev parent reply other threads:[~2006-08-04 15:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 11:05 [PATCH 3/4] Add /proc/sys/fs/nfs sysctls to nfsd module Olaf Kirch
2006-08-03 16:52 ` Chuck Lever
2006-08-03 17:08 ` Trond Myklebust
2006-08-04 17:55 ` Olaf Kirch
2006-08-04 8:43 ` Greg Banks
2006-08-04 15:36 ` Trond Myklebust [this message]
2006-08-04 17:52 ` Olaf Kirch
2006-08-04 18:23 ` Trond Myklebust
2006-08-04 19:16 ` Peter Staubach
2006-08-04 20:06 ` Olaf Kirch
2006-08-07 4:02 ` Trond Myklebust
2006-08-04 23:36 ` Neil Brown
2006-08-05 13:15 ` Olaf Kirch
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=1154705797.4727.18.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=chucklever@gmail.com \
--cc=gnb@melbourne.sgi.com \
--cc=nfs@lists.sourceforge.net \
--cc=okir@suse.de \
/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