From: Chuck Lever <cel@kernel.org>
To: NeilBrown <neil@brown.name>, Jeff Layton <jlayton@kernel.org>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <dai.ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Cc: <linux-nfs@vger.kernel.org>, Chuck Lever <chuck.lever@oracle.com>
Subject: [PATCH v2 0/2] NFSD duplicate reply cache optimizations
Date: Thu, 21 Aug 2025 10:53:19 -0400 [thread overview]
Message-ID: <20250821145321.7662-1-cel@kernel.org> (raw)
From: Chuck Lever <chuck.lever@oracle.com>
Two minor optimizations for the NFSD duplicate reply cache. These
showed slight improvement in WRITE throughput on exported fast
file systems.
Changes since v1:
- Remove RC_INPROG check from nfsd_prune_bucket_locked()
Chuck Lever (2):
NFSD: Delay adding new entries to LRU
NFSD: Reduce DRC bucket size
fs/nfsd/nfscache.c | 15 +--------------
1 file changed, 1 insertion(+), 14 deletions(-)
--
2.50.0
next reply other threads:[~2025-08-21 14:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 14:53 Chuck Lever [this message]
2025-08-21 14:53 ` [PATCH v2 1/2] NFSD: Delay adding new entries to LRU Chuck Lever
2025-08-21 14:53 ` [PATCH v2 2/2] NFSD: Reduce DRC bucket size 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=20250821145321.7662-1-cel@kernel.org \
--to=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=dai.ngo@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--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