From: Jeff Layton <jlayton@kernel.org>
To: chuck.lever@oracle.com
Cc: linux-nfs@vger.kernel.org, neilb@suse.de
Subject: [PATCH v2 0/3] nfsd: clean up refcounting in filecache
Date: Thu, 27 Oct 2022 17:52:10 -0400 [thread overview]
Message-ID: <20221027215213.138304-1-jlayton@kernel.org> (raw)
This patchset should bring the filecache into closer alignment with what
Neil had mentioned here. The first patch cleans up the refcounting, and
the second two optimize the "gc" entry handling.
This should apply cleanly on top of Chuck's current for-next branch.
Jeff Layton (3):
nfsd: rework refcounting in filecache
nfsd: only keep unused entries on the LRU
nfsd: start non-blocking writeback after adding nfsd_file to the LRU
fs/nfsd/filecache.c | 331 ++++++++++++++++++++++++--------------------
fs/nfsd/trace.h | 5 +-
2 files changed, 185 insertions(+), 151 deletions(-)
--
2.37.3
next reply other threads:[~2022-10-27 21:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 21:52 Jeff Layton [this message]
2022-10-27 21:52 ` [PATCH v2 1/3] nfsd: rework refcounting in filecache Jeff Layton
2022-10-27 22:51 ` NeilBrown
2022-10-28 9:57 ` Jeff Layton
2022-10-28 22:14 ` NeilBrown
2022-10-30 21:29 ` NeilBrown
2022-10-31 9:58 ` Jeff Layton
2022-10-31 9:54 ` Jeff Layton
2022-10-27 21:52 ` [PATCH v2 2/3] nfsd: only keep unused entries on the LRU Jeff Layton
2022-10-27 22:20 ` NeilBrown
2022-10-27 22:47 ` Jeff Layton
2022-10-27 22:55 ` NeilBrown
2022-10-27 23:52 ` Chuck Lever III
2022-10-27 21:52 ` [PATCH v2 3/3] nfsd: start non-blocking writeback after adding nfsd_file to " Jeff Layton
2022-10-27 22:25 ` NeilBrown
2022-10-28 13:01 ` Jeff Layton
2022-10-28 13:16 ` Chuck Lever III
2022-10-28 15:05 ` Jeff Layton
2022-10-28 15:29 ` Chuck Lever III
2022-10-28 15:51 ` Jeff Layton
2022-10-28 17:21 ` Chuck Lever III
2022-10-28 17:43 ` Jeff Layton
2022-10-28 18:53 ` Chuck Lever III
2022-10-28 20:04 ` Jeff Layton
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=20221027215213.138304-1-jlayton@kernel.org \
--to=jlayton@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
/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