From: NeilBrown <neilb@ownmail.net>
To: Chuck Lever <chuck.lever@oracle.com>, Jeff Layton <jlayton@kernel.org>
Cc: Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
linux-nfs@vger.kernel.org
Subject: [PATCH 0/2] cleanups in nfs4reovery.c
Date: Mon, 8 Sep 2025 11:38:31 +1000 [thread overview]
Message-ID: <20250908014348.329348-1-neilb@ownmail.net> (raw)
This first of these patchs is part of my work to change how directory
locking is managed. That will involve moving the lock as close as possible
to the operation being locked, and using some standard interfaces
which combine the lock and the lookup. Then changing the mechanics of
taking a lock.
nfsd4_list_rec_dir() currenty locks a direct and performs a lookup
in a different function to where the lock and lookup results are needed,
and does it even when those are not needed at all. So the first
patch moves the lock and lookup to where it is needed.
The second patch (arguably) improves the calling protocol for
nfs4_client_to_reclaim(). If people don't like this second patch I'm
happy for it to be dropped. It is the first patch which is particularly
important to me.
Thanks,
NeilBrown
[PATCH 1/2] nfsd: move name lookup out of nfsd4_list_rec_dir()
[PATCH 2/2] nfsd: change nfs4_client_to_reclaim() to allocate data
next reply other threads:[~2025-09-08 1:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 1:38 NeilBrown [this message]
2025-09-08 1:38 ` [PATCH 1/2] nfsd: move name lookup out of nfsd4_list_rec_dir() NeilBrown
2025-09-08 1:38 ` [PATCH 2/2] nfsd: change nfs4_client_to_reclaim() to allocate data NeilBrown
2025-09-08 14:36 ` [PATCH 0/2] cleanups in nfs4reovery.c Chuck Lever
2025-09-08 19:40 ` Jeff Layton
2025-09-08 20:02 ` Chuck Lever
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=20250908014348.329348-1-neilb@ownmail.net \
--to=neilb@ownmail.net \
--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