From: NeilBrown <neilb@suse.de>
To: Chuck Lever <chuck.lever@oracle.com>, Jeff Layton <jlayton@kernel.org>
Cc: linux-nfs@vger.kernel.org,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Subject: [PATCH 0/6 v3] nfsd: allocate/free session-based DRC slots on demand
Date: Fri, 6 Dec 2024 11:43:14 +1100 [thread overview]
Message-ID: <20241206004829.3497925-1-neilb@suse.de> (raw)
Changes from v2:
- number of slots is increased more quickly. Every time the highest-number
slot is used, we increase by at least 20%.
- when xa_store() is used in a context where we no that no allocation can
happen, pass '0' as the GFP flag.
- report target slots as well as total slots in /proc/fs/nfsd/clients/*/info
I've stay with reporting session information in the client info file
rather than creating a directory or using netlink. I think the client
info file is simple and adequate.
I still haven't added support for CB_RECALL_SLOT. While it is helpful,
it isn't essential. I'll probably try to add it after the current
series lands.
Thanks,
NeilBrown
next reply other threads:[~2024-12-06 0:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 0:43 NeilBrown [this message]
2024-12-06 0:43 ` [PATCH 1/6] nfsd: use an xarray to store v4.1 session slots NeilBrown
2024-12-06 0:43 ` [PATCH 2/6] nfsd: remove artificial limits on the session-based DRC NeilBrown
2024-12-06 0:43 ` [PATCH 3/6] nfsd: add session slot count to /proc/fs/nfsd/clients/*/info NeilBrown
2024-12-06 0:43 ` [PATCH 4/6] nfsd: allocate new session-based DRC slots on demand NeilBrown
2024-12-06 1:04 ` Jeff Layton
2024-12-06 1:43 ` NeilBrown
2024-12-06 13:49 ` Jeff Layton
2024-12-06 20:51 ` Chuck Lever
2024-12-08 4:52 ` NeilBrown
2024-12-06 0:43 ` [PATCH 5/6] nfsd: add support for freeing unused session-DRC slots NeilBrown
2024-12-06 5:30 ` Jeff Layton
2024-12-06 6:05 ` NeilBrown
2024-12-06 13:59 ` Jeff Layton
2024-12-06 0:43 ` [PATCH 6/6] nfsd: add shrinker to reduce number of slots allocated per session NeilBrown
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=20241206004829.3497925-1-neilb@suse.de \
--to=neilb@suse.de \
--cc=Dai.Ngo@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=okorniev@redhat.com \
--cc=tom@talpey.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox