From: Ben Myers <bpm@sgi.com>
To: linux-nfs@vger.kernel.org
Subject: [PATCH 0/2] knfsd: support larger numbers of clients
Date: Mon, 22 Feb 2010 15:54:37 -0600 [thread overview]
Message-ID: <20100222215349.8481.80700.stgit@case> (raw)
Several customers that have large numbers of nfs clients have run afoul of the
existing connection limits ((nr_threads+3) * 20) and have been handling the
situation by bumping the number of nfsd threads. There are two problems:
1) The maximum number of connections is tied to the number of nfsd threads.
The first patch decouples the maximum number of connections from the number of
threads by making it a tuneable. Note that the default setting still uses the
existing formula. Folks who want to handle additional connections without
bumping the number of threads can do so.
2) At around 1020 threads the send buffer size wraps negative and things grind
to a halt.
The second patch decouples the size of send and receive buffers from the number
of threads by making them tuneable. Buffer sizes were getting absurdly large
as the number of nfsd threads grew. Now they remain constant.
Both patches were originally implmented using sysctls but I have changed them
over to module parameters to match what Jeff Layton has done with
nlm_max_connections.
Thanks,
Ben
---
Ben Myers (2):
knfsd: nfsd_max_connections module parameter
sunrpc: socket buffer size module parameter
fs/nfsd/nfsctl.c | 7 ++++
fs/nfsd/nfssvc.c | 3 ++
net/sunrpc/sunrpc_syms.c | 39 ++++++++++++++++++++++
net/sunrpc/svcsock.c | 81 +++++++++++++++++++++++-----------------------
4 files changed, 89 insertions(+), 41 deletions(-)
--
next reply other threads:[~2010-02-22 21:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-22 21:54 Ben Myers [this message]
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
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=20100222215349.8481.80700.stgit@case \
--to=bpm@sgi.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