From: "J. Bruce Fields" <bfields@redhat.com>
To: linux-nfs@vger.kernel.org
Cc: "J. Bruce Fields" <bfields@redhat.com>
Subject: [PATCH 0/2] tweak knfsd session slot table sizing
Date: Mon, 25 Sep 2017 09:21:42 -0400 [thread overview]
Message-ID: <1506345704-9486-1-git-send-email-bfields@redhat.com> (raw)
From: "J. Bruce Fields" <bfields@redhat.com>
Current client and server defaults can limit NFSv4.1+ mounts to as few
as 4 per gigabytes of server RAM, and people have been running into the
limit on upgrading the protocol version from 4.0 to 4.1.
Bump the limit. Also return smaller ca_maxrequests as the limit
approaches instead of waiting till we have to fail CREATE_SESSION
completely.
A few years ago Trond also posted some patches to dynamically resize
existing sessions as limits approach--I'll revisit those at some point
too.
The numbers chosen here are honestly still a little arbitrary, and we
may tweak them again if we see more problems.
--b.
J. Bruce Fields (2):
nfsd: increase DRC cache limit
nfsd: give out fewer session slots as limit approaches
fs/nfsd/nfs4state.c | 5 +++++
fs/nfsd/nfssvc.c | 2 +-
2 files changed, 6 insertions(+), 1 deletion(-)
--
2.13.5
next reply other threads:[~2017-09-25 13:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 13:21 J. Bruce Fields [this message]
2017-09-25 13:21 ` [PATCH 1/2] nfsd: increase DRC cache limit J. Bruce Fields
2017-09-25 13:21 ` [PATCH 2/2] nfsd: give out fewer session slots as limit approaches J. Bruce Fields
2019-09-19 1:08 ` NeilBrown
2019-09-19 16:22 ` J. Bruce Fields
2019-09-19 17:17 ` J. Bruce Fields
2019-09-19 18:41 ` J. Bruce Fields
2019-09-20 6:15 ` [PATCH 1/2] nfsd: handle drc over-allocation gracefully NeilBrown
2019-09-20 6:33 ` [PATCH 1/2 - vers2] " NeilBrown
2019-09-20 6:36 ` [PATCH - 2/2] nfsd: degraded slot-count more gracefully as allocation nears exhaustion NeilBrown
2019-09-20 16:28 ` [PATCH 1/2 - vers2] nfsd: handle drc over-allocation gracefully J. Bruce Fields
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=1506345704-9486-1-git-send-email-bfields@redhat.com \
--to=bfields@redhat.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;
as well as URLs for NNTP newsgroup(s).