From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs: minor cleanup related to bitmap operations
Date: Wed, 10 Dec 2025 19:02:32 +1030 [thread overview]
Message-ID: <cover.1765354917.git.wqu@suse.com> (raw)
This is the safer cleanup part extracted from the previous attempt:
https://lore.kernel.org/linux-btrfs/cover.1763629982.git.wqu@suse.com/
The first patch is to concentrate the error handling of
submit_one_sector() so we do not have two separate error handling.
The second patch is the convert for_each_set_bit() to a more efficient
for_each_set_bitmap() so that we can benefit from functions which
accept a range other than a single block.
Qu Wenruo (2):
btrfs: integrate the error handling of submit_one_sector()
btrfs: replace for_each_set_bit() with for_each_set_bitmap()
fs/btrfs/extent_io.c | 55 +++++++++++++++++++++++++-------------------
1 file changed, 31 insertions(+), 24 deletions(-)
--
2.52.0
next reply other threads:[~2025-12-10 8:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 8:32 Qu Wenruo [this message]
2025-12-10 8:32 ` [PATCH 1/2] btrfs: integrate the error handling of submit_one_sector() Qu Wenruo
2025-12-10 8:32 ` [PATCH 2/2] btrfs: replace for_each_set_bit() with for_each_set_bitmap() Qu Wenruo
2025-12-11 18:40 ` [PATCH 0/2] btrfs: minor cleanup related to bitmap operations 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.1765354917.git.wqu@suse.com \
--to=wqu@suse.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.