public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: kunwu.chan@linux.dev
Cc: chandan.babu@oracle.com, linux-xfs@vger.kernel.org,
	linux-kernel@vger.kernel.org, Kunwu Chan <chentao@kylinos.cn>
Subject: Re: [PATCH] xfs: use KMEM_CACHE() to create xfs_defer_pending cache
Date: Thu, 29 Feb 2024 08:00:49 -0800	[thread overview]
Message-ID: <20240229160049.GY1927156@frogsfrogsfrogs> (raw)
In-Reply-To: <20240229083342.1128686-1-kunwu.chan@linux.dev>

On Thu, Feb 29, 2024 at 04:33:42PM +0800, kunwu.chan@linux.dev wrote:
> From: Kunwu Chan <chentao@kylinos.cn>
> 
> Use the KMEM_CACHE() macro instead of kmem_cache_create() to simplify
> the creation of SLAB caches when the default values are used.
> 
> Signed-off-by: Kunwu Chan <chentao@kylinos.cn>

Why bother? The vast majority of the kernel is still using
kmem_cache_create(), not the weird, shouty macro that doesn't actually
tell us what it is doing with said kmem_cache......

Up until now we've chosen not switch XFS to use it because many of the
slab caches we use in XFS are not just "default" slab caches.  IOWs, we
still have to use kmem_cache_create() for a lot of the caches we create,
so we may as well use kmem_cache_create() for all of them rather than
have to go look up what KMEM_CACHE() translates to every time we are
looking at how slab caches are created.

Also, if you are going to change simple API stuff like this in XFS,
please do all the conversions in a single patch. It takes much less time
and resources to review and merge a single patch compared to a pile of
dozen independent one line patches...

--D

> ---
>  fs/xfs/libxfs/xfs_defer.c | 4 +---
>  1 file changed, 1 insertion(+), 3 deletions(-)
> 
> diff --git a/fs/xfs/libxfs/xfs_defer.c b/fs/xfs/libxfs/xfs_defer.c
> index 66a17910d021..6d957fcc17f2 100644
> --- a/fs/xfs/libxfs/xfs_defer.c
> +++ b/fs/xfs/libxfs/xfs_defer.c
> @@ -1143,9 +1143,7 @@ xfs_defer_resources_rele(
>  static inline int __init
>  xfs_defer_init_cache(void)
>  {
> -	xfs_defer_pending_cache = kmem_cache_create("xfs_defer_pending",
> -			sizeof(struct xfs_defer_pending),
> -			0, 0, NULL);
> +	xfs_defer_pending_cache = KMEM_CACHE(xfs_defer_pending, 0);
>  
>  	return xfs_defer_pending_cache != NULL ? 0 : -ENOMEM;
>  }
> -- 
> 2.39.2
> 
> 

  reply	other threads:[~2024-02-29 16:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29  8:33 [PATCH] xfs: use KMEM_CACHE() to create xfs_defer_pending cache kunwu.chan
2024-02-29 16:00 ` Darrick J. Wong [this message]
2024-02-29 23:26 ` Dave Chinner
2024-03-01  2:02   ` Kunwu Chan

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=20240229160049.GY1927156@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=chandan.babu@oracle.com \
    --cc=chentao@kylinos.cn \
    --cc=kunwu.chan@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@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