From: Trond Myklebust <trondmy@gmail.com>
To: Anna Schumaker <Anna.Schumaker@netapp.com>
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/5] Fix up delegation management
Date: Mon, 27 Jan 2020 09:58:14 -0500 [thread overview]
Message-ID: <20200127145819.350982-1-trond.myklebust@hammerspace.com> (raw)
Delegations allow the client to cache various objects aggressively,
however they can also be a source of scalability issues on the server
if not returned when not it use.
The following patchset allows the client to set a limit on the number
of delegations that it holds. Once it hits that limit, it starts to
return the delegations on close in order to avoid swamping the server
with state.
Trond Myklebust (5):
NFSv4: nfs_inode_evict_delegation() should set
NFS_DELEGATION_RETURNING
NFS: Clear NFS_DELEGATION_RETURN_IF_CLOSED when the delegation is
returned
NFSv4: Try to return the delegation immediately when marked for return
on close
NFSv4: Add accounting for the number of active delegations held
NFSv4: Limit the total number of cached delegations
fs/nfs/delegation.c | 80 +++++++++++++++++++++++++++++++++++++--------
fs/nfs/delegation.h | 1 +
fs/nfs/nfs4state.c | 1 +
3 files changed, 69 insertions(+), 13 deletions(-)
--
2.24.1
next reply other threads:[~2020-01-27 15:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 14:58 Trond Myklebust [this message]
2020-01-27 14:58 ` [PATCH 1/5] NFSv4: nfs_inode_evict_delegation() should set NFS_DELEGATION_RETURNING Trond Myklebust
2020-01-27 14:58 ` [PATCH 2/5] NFS: Clear NFS_DELEGATION_RETURN_IF_CLOSED when the delegation is returned Trond Myklebust
2020-01-27 14:58 ` [PATCH 3/5] NFSv4: Try to return the delegation immediately when marked for return on close Trond Myklebust
2020-01-27 14:58 ` [PATCH 4/5] NFSv4: Add accounting for the number of active delegations held Trond Myklebust
2020-01-27 14:58 ` [PATCH 5/5] NFSv4: Limit the total number of cached delegations Trond Myklebust
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=20200127145819.350982-1-trond.myklebust@hammerspace.com \
--to=trondmy@gmail.com \
--cc=Anna.Schumaker@netapp.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).