From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Tom Georgoulias <tom.georgoulias@motorola.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: max memory size on input queue?
Date: 04 Jun 2003 19:33:35 +0200 [thread overview]
Message-ID: <shs1xy9928g.fsf@charged.uio.no> (raw)
In-Reply-To: <3EDE192D.4000602@motorola.com>
>>>>> " " == Tom Georgoulias <tom.georgoulias@motorola.com> writes:
> Is there any agreement on what is the safest, largest input
> queue memory size? /etc/syconfig/nfs has an option to turn
> this value to 256k, so it that generally the best setting to
> use? What about 512k?
See the discussion in the NFS-HOWTO.
Cheers,
Trond
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2003-06-04 17:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-04 16:07 max memory size on input queue? Tom Georgoulias
2003-06-04 17:12 ` Matt Schillinger
2003-06-04 17:33 ` Trond Myklebust [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=shs1xy9928g.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=nfs@lists.sourceforge.net \
--cc=tom.georgoulias@motorola.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.