From: trondmy@kernel.org
To: linux-nfs@vger.kernel.org
Subject: [PATCH 0/4] Fixes for looping in the NFSv4 manager thread
Date: Mon, 3 Mar 2025 12:35:25 -0500 [thread overview]
Message-ID: <cover.1741023037.git.trond.myklebust@hammerspace.com> (raw)
From: Trond Myklebust <trond.myklebust@hammerspace.com>
The following set of patches address an issue where the NFSv4 manager
thread can end up doing a lot of looping in order to do asynchronous
returns of old delegations. When the list of cached delegations gets
large enough, this can sometimes lead to soft lockups being declared.
Trond Myklebust (4):
NFSv4: Don't trigger uneccessary scans for return-on-close delegations
NFSv4: Avoid unnecessary scans of filesystems for returning
delegations
NFSv4: Avoid unnecessary scans of filesystems for expired delegations
NFSv4: Avoid unnecessary scans of filesystems for delayed delegations
fs/nfs/delegation.c | 63 ++++++++++++++++++++++++++-------------
include/linux/nfs_fs_sb.h | 4 +++
2 files changed, 46 insertions(+), 21 deletions(-)
--
2.48.1
next reply other threads:[~2025-03-03 17:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 17:35 trondmy [this message]
2025-03-03 17:35 ` [PATCH 1/4] NFSv4: Don't trigger uneccessary scans for return-on-close delegations trondmy
2025-03-03 17:35 ` [PATCH 2/4] NFSv4: Avoid unnecessary scans of filesystems for returning delegations trondmy
2025-03-03 17:35 ` [PATCH 3/4] NFSv4: Avoid unnecessary scans of filesystems for expired delegations trondmy
2025-03-03 17:35 ` [PATCH 4/4] NFSv4: Avoid unnecessary scans of filesystems for delayed delegations trondmy
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=cover.1741023037.git.trond.myklebust@hammerspace.com \
--to=trondmy@kernel.org \
--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