Linux NFS development
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@lucon.org>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Sean O'Connell <sean@ee.duke.edu>, nfs@lists.sourceforge.net
Subject: Re: Re: Proposed changes for init file in nfs-utils
Date: Sun, 7 Apr 2002 20:10:43 -0700	[thread overview]
Message-ID: <20020407201043.A17954@lucon.org> (raw)
In-Reply-To: <15537.823.811512.451102@notabene.cse.unsw.edu.au>; from neilb@cse.unsw.edu.au on Mon, Apr 08, 2002 at 12:40:55PM +1000

On Mon, Apr 08, 2002 at 12:40:55PM +1000, Neil Brown wrote:
> On Sunday April 7, hjl@lucon.org wrote:
> > 
> > I checked a slightly different patch. Please check it out and make
> > sure I didn't break anything.
> 
> ...
> > +	if [ "$TUNE_QUEUE" = "yes" ]; then
> > + 	    /sbin/sysctl -w net.core.rmem_default=$NFSD_QS >/dev/null 2>&1
> > +	    /sbin/sysctl -w net.core.rmem_max=$NFSD_QS >/dev/null 2>&1
> > +	    /sbin/sysctl -w net.core.wmem_default=$NFSD_QS >/dev/null 2>&1
> > +	    /sbin/sysctl -w net.core.wmem_max=$NFSD_QS >/dev/null 2>&1
> > +	fi
> 
> Though it possibly doesn't hurt, there is nothing to be gained by
> setting the wmem_{default,max}.
> Only the rmem needs to be set.  This is because nfsd doesn't take
> packets off the udp queue until they are completely processed, so the
> rmem_{default,max} needs to be big enough to hold all currently active
> requests.
> 

I guess I don't have to tell you feel free to make any necessary
changes :-).


H.J.

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      reply	other threads:[~2002-04-08  3:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020406205304.C2076@ee.duke.edu>
2002-04-07 20:55 ` Proposed changes for init file in nfs-utils H . J . Lu
2002-04-08  2:40   ` Neil Brown
2002-04-08  3:10     ` H . J . Lu [this message]

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=20020407201043.A17954@lucon.org \
    --to=hjl@lucon.org \
    --cc=neilb@cse.unsw.edu.au \
    --cc=nfs@lists.sourceforge.net \
    --cc=sean@ee.duke.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