Linux NFS development
 help / color / mirror / Atom feed
From: Johan van den Dorpe <johan.vandendorpe@framestore-cfc.com>
To: nfs@lists.sourceforge.net
Subject: network socket buffers & file descriptor questions
Date: Fri, 19 Mar 2004 17:14:13 +0000	[thread overview]
Message-ID: <405B2A65.2080703@framestore-cfc.com> (raw)

Hi,

I wanted to clarify a couple of things that I've failed to understand 
fully after reading the FAQ, books, reading list archives and doing web 
searches.

Socket input buffers- some documentation I've read suggests that these 
are tuned dymanically for TCP but need to be manually tuned for UDP in
/proc/sys/net/core/rmem_default and rmem_max

Elsewhere I've read that "for kernels later than about 2.4.20-pre4, this 
setting is not needed and is ignored.  The nfsd code does 'the right 
thing'. The setting is only needed for earlier kernels."

Is this true for both UDP and TCP or only for TCP?


Second, what is the default amount of file descriptors available to 
rpc.mountd?

The man page that comes with nfs-utils 1.06 says "The default is to 
leave the limit unchanged." Older manpages seem to suggest that the 
limit was once 256. Is the number drawn from the default shell limit?


Thanks,

-- 
Johan van den Dorpe


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

                 reply	other threads:[~2004-03-19 17:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=405B2A65.2080703@framestore-cfc.com \
    --to=johan.vandendorpe@framestore-cfc.com \
    --cc=nfs@lists.sourceforge.net \
    /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