From: bpm@sgi.com
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 2/2] sunrpc: socket buffer size module parameter
Date: Tue, 23 Feb 2010 10:12:24 -0600 [thread overview]
Message-ID: <20100223161224.GG10942@sgi.com> (raw)
In-Reply-To: <4B833056.8020703@oracle.com>
Hey Chuck,
On Mon, Feb 22, 2010 at 05:33:10PM -0800, Chuck Lever wrote:
> On 02/22/2010 01:54 PM, Ben Myers wrote:
>> +int tcp_rcvbuf_nrpc = 6;
>
> Just curious, is this '6' a typo?
Not a typo. The original setting for tcp receive buffer was hardcoded
at
3 (in svc_tcp_init and svc_tcp_recv_record)
*
sv_max_mesg
*
2 (in svc_sock_setbufsize)
That's where I came up with the 6 for the tcp recv buffer. The setting
hasn't changed.
The UDP send/recv buffer settings and TCP send buffer settings were
going to be
( 4 (default number of kernel threads on sles11)
+
3 (as in svc_udp_recvfrom, etc) )
*
sv_max_mesg
*
2 (in svc_sock_setbufsize)
but 14 wasn't a very round number, so I went with 16 which also happened
to match the slot_table_entries default.
> Perhaps it would be nice to have a
> single macro defined as the default value for all of these.
>
> Do we have a high degree of confidence that these new default settings
> will not adversely affect workloads that already perform well?
This patch has been in several releases of SGI's nfsd respin and I've
heard nothing to suggest there is an issue. I didn't spend much time
taking measurements on UDP and didn't keep my TCP measurements. If you
feel measurements are essential I'll be happy to provide a few, but
won't be able to get around to it for a little while.
Thanks,
Ben
next prev parent reply other threads:[~2010-02-23 16:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-22 21:54 [PATCH 0/2] knfsd: support larger numbers of clients Ben Myers
2010-02-22 21:54 ` [PATCH 1/2] knfsd: nfsd_max_connections module parameter Ben Myers
2010-02-22 21:54 ` [PATCH 2/2] sunrpc: socket buffer size " Ben Myers
2010-02-23 1:33 ` Chuck Lever
2010-02-23 16:12 ` bpm [this message]
2010-02-23 20:09 ` Chuck Lever
2010-02-23 20:48 ` bpm
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=20100223161224.GG10942@sgi.com \
--to=bpm@sgi.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
/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