From: "Andrew Theurer" <habanero@us.ibm.com>
To: "Bill Rugolsky Jr." <brugolsky@yahoo.com>
Cc: <nfs@lists.sourceforge.net>
Subject: Re: RPC error on NFS over TCP
Date: Tue, 26 Mar 2002 09:27:31 -0600 [thread overview]
Message-ID: <002d01c1d4da$c00d2310$2d060e09@beavis> (raw)
In-Reply-To: 20020326071622.A28115@ead45
> On Mon, Mar 25, 2002 at 06:05:03PM -0600, Andrew Theurer wrote:
> > The linux server is kernel 2.4.18 (with Neil's patches) and sometimes
2.5.7.
> > The clients (48 of them) are mostly just RH-2.4.2-2 and one is 2.5.7
(happens
> > on both kernels). There are no dropped packets reported on ifconfig.
There
> > are RPC retransmits on the clients. Any ideas?
>
> You may need more threads to service the clients? See Neil's notes
> that accompanied the patches (in the archives) w.r.t the number of threads
> and the number of RPC receive buffers.
Thanks Bill! I tried 128 threads and it seems to be OK so far.
-Andrew
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2002-03-26 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-26 0:05 RPC error on NFS over TCP Andrew Theurer
[not found] ` <20020326071622.A28115@ead45>
2002-03-26 15:27 ` Andrew Theurer [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='002d01c1d4da$c00d2310$2d060e09@beavis' \
--to=habanero@us.ibm.com \
--cc=brugolsky@yahoo.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