mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kunwu Chan <chentao@kylinos.cn>
To: clm@fb.com, josef@toxicpanda.com, dsterba@suse.com
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	Kunwu Chan <chentao@kylinos.cn>
Subject: [PATCH 0/6] btrfs: Use KMEM_CACHE instead of kmem_cache_create
Date: Tue, 20 Feb 2024 17:06:39 +0800	[thread overview]
Message-ID: <20240220090645.108625-1-chentao@kylinos.cn> (raw)

As David Sterba said in 
https://lore.kernel.org/all/20240205160408.GI355@twin.jikos.cz/
I'm using a patchset to cleanup the same issues in the 'brtfs' module.

For where the cache name and the structure name match.
Use the new KMEM_CACHE() macro instead of direct kmem_cache_create
to simplify the creation of SLAB caches.

Kunwu Chan (6):
  btrfs: Simplify the allocation of slab caches in
    btrfs_delayed_inode_init
  btrfs: Simplify the allocation of slab caches in ordered_data_init
  btrfs: Simplify the allocation of slab caches in
    btrfs_transaction_init
  btrfs: Simplify the allocation of slab caches in btrfs_ctree_init
  btrfs: Simplify the allocation of slab caches in
    btrfs_delayed_ref_init
  btrfs: Simplify the allocation of slab caches in btrfs_free_space_init

 fs/btrfs/ctree.c            |  4 +---
 fs/btrfs/delayed-inode.c    |  6 +-----
 fs/btrfs/delayed-ref.c      | 24 ++++++++----------------
 fs/btrfs/free-space-cache.c |  4 +---
 fs/btrfs/ordered-data.c     |  5 +----
 fs/btrfs/transaction.c      |  5 ++---
 6 files changed, 14 insertions(+), 34 deletions(-)

-- 
2.39.2


             reply	other threads:[~2024-02-20  9:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-20  9:06 Kunwu Chan [this message]
2024-02-20  9:06 ` [PATCH 1/6] btrfs: Simplify the allocation of slab caches in btrfs_delayed_inode_init Kunwu Chan
2024-02-20  9:06 ` [PATCH 2/6] btrfs: Simplify the allocation of slab caches in ordered_data_init Kunwu Chan
2024-02-20  9:06 ` [PATCH 3/6] btrfs: Simplify the allocation of slab caches in btrfs_transaction_init Kunwu Chan
2024-02-20  9:06 ` [PATCH 4/6] btrfs: Simplify the allocation of slab caches in btrfs_ctree_init Kunwu Chan
2024-02-20  9:06 ` [PATCH 5/6] btrfs: Simplify the allocation of slab caches in btrfs_delayed_ref_init Kunwu Chan
2024-02-20  9:06 ` [PATCH 6/6] btrfs: Simplify the allocation of slab caches in btrfs_free_space_init Kunwu Chan
2024-02-21 12:00 ` [PATCH 0/6] btrfs: Use KMEM_CACHE instead of kmem_cache_create David Sterba
2024-02-22  3:10   ` 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=20240220090645.108625-1-chentao@kylinos.cn \
    --to=chentao@kylinos.cn \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®