Linux NFS development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Chuck Lever <cel@kernel.org>, linux-nfs@vger.kernel.org
Cc: Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [PATCH v1 0/6] Fix some lock contention in the NFS server's DRC
Date: Mon, 10 Jul 2023 09:03:06 -0400	[thread overview]
Message-ID: <35ca6665f3cbedb60b904bfe4e74ca37c32af985.camel@kernel.org> (raw)
In-Reply-To: <168891733570.3964.15456501153247760888.stgit@manet.1015granger.net>

On Sun, 2023-07-09 at 11:45 -0400, Chuck Lever wrote:
> This series optimizes DRC scalability by freeing cache objects only
> once the hash bucket lock is no longer held. There are a couple of
> related clean-ups to go along with this optimization.
> 


The conventional wisdom that I've always heard is that a kfree under
spinlock is generally no big deal. It can't block and is usually quite
fast. Are you able to measure any performance delta from this set?



> ---
> 
> Chuck Lever (6):
>       NFSD: Refactor nfsd_reply_cache_free_locked()
>       NFSD: Rename nfsd_reply_cache_alloc()
>       NFSD: Replace nfsd_prune_bucket()
>       NFSD: Refactor the duplicate reply cache shrinker
>       NFSD: Remove svc_rqst::rq_cacherep
>       NFSD: Rename struct svc_cacherep
> 
> 
>  fs/nfsd/cache.h            |   8 +-
>  fs/nfsd/nfscache.c         | 203 ++++++++++++++++++++++++-------------
>  fs/nfsd/nfssvc.c           |  10 +-
>  fs/nfsd/trace.h            |  26 ++++-
>  include/linux/sunrpc/svc.h |   1 -
>  5 files changed, 165 insertions(+), 83 deletions(-)
> 
> --
> Chuck Lever
> 

-- 
Jeff Layton <jlayton@kernel.org>

  parent reply	other threads:[~2023-07-10 13:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-09 15:45 [PATCH v1 0/6] Fix some lock contention in the NFS server's DRC Chuck Lever
2023-07-09 15:45 ` [PATCH v1 1/6] NFSD: Refactor nfsd_reply_cache_free_locked() Chuck Lever
2023-07-10 13:09   ` Jeff Layton
2023-07-09 15:45 ` [PATCH v1 2/6] NFSD: Rename nfsd_reply_cache_alloc() Chuck Lever
2023-07-09 15:45 ` [PATCH v1 3/6] NFSD: Replace nfsd_prune_bucket() Chuck Lever
2023-07-09 15:45 ` [PATCH v1 4/6] NFSD: Refactor the duplicate reply cache shrinker Chuck Lever
2023-07-09 15:45 ` [PATCH v1 5/6] NFSD: Remove svc_rqst::rq_cacherep Chuck Lever
2023-07-10 13:17   ` Jeff Layton
2023-07-09 15:45 ` [PATCH v1 6/6] NFSD: Rename struct svc_cacherep Chuck Lever
2023-07-10 13:03 ` Jeff Layton [this message]
2023-07-10 13:47   ` [PATCH v1 0/6] Fix some lock contention in the NFS server's DRC Chuck Lever III
2023-07-10 13:19 ` 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=35ca6665f3cbedb60b904bfe4e74ca37c32af985.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=cel@kernel.org \
    --cc=chuck.lever@oracle.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