From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/3] btrfs: use refcount_t type for extent buffers and cleanups
Date: Tue, 3 Jun 2025 15:50:24 +0100 [thread overview]
Message-ID: <cover.1748962110.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
Switch from a bare atomic to refcount_t type to track extent buffer
reference count and a couple cleanups. Details in the change logs.
Filipe Manana (3):
btrfs: reorganize logic at free_extent_buffer() for better readability
btrfs: add comment for optimization in free_extent_buffer()
btrfs: use refcount_t type for the extent buffer reference counter
fs/btrfs/ctree.c | 14 ++++-----
fs/btrfs/extent-tree.c | 2 +-
fs/btrfs/extent_io.c | 55 +++++++++++++++++++-----------------
fs/btrfs/extent_io.h | 2 +-
fs/btrfs/fiemap.c | 2 +-
fs/btrfs/print-tree.c | 2 +-
fs/btrfs/qgroup.c | 6 ++--
fs/btrfs/relocation.c | 4 +--
fs/btrfs/tree-log.c | 4 +--
fs/btrfs/zoned.c | 2 +-
include/trace/events/btrfs.h | 2 +-
11 files changed, 49 insertions(+), 46 deletions(-)
--
2.47.2
next reply other threads:[~2025-06-03 14:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 14:50 fdmanana [this message]
2025-06-03 14:50 ` [PATCH 1/3] btrfs: reorganize logic at free_extent_buffer() for better readability fdmanana
2025-06-03 21:05 ` David Sterba
2025-06-03 14:50 ` [PATCH 2/3] btrfs: add comment for optimization in free_extent_buffer() fdmanana
2025-06-03 14:50 ` [PATCH 3/3] btrfs: use refcount_t type for the extent buffer reference counter fdmanana
2025-06-03 19:30 ` [PATCH 0/3] btrfs: use refcount_t type for extent buffers and cleanups Boris Burkov
2025-06-03 20:25 ` David Sterba
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=cover.1748962110.git.fdmanana@suse.com \
--to=fdmanana@kernel.org \
--cc=linux-btrfs@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