From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/4] btrfs: reduce btrfs_get_extent() calls for buffered write path
Date: Thu, 20 Nov 2025 10:34:29 +1030 [thread overview]
Message-ID: <cover.1763596717.git.wqu@suse.com> (raw)
Although btrfs has bs < ps support for a long time, and the larger data
folios support is also going to be graduate from experimental features
soon, the write path is still iterating each fs block and call
btrfs_get_extent() on each fs block.
What makes the situation worse is that, for the write path we do not
have any cached extent map, meaning even with large folios and we got a
continuous range that can be submitted in one go, we still call
btrfs_get_extent() many times and get the same range extent map again
and again.
This series will reduce the duplicated btrfs_get_extent() calls by only
call it once for each range, other than for each fs block.
The first 3 patches are just minor cleanups/refactors, the last patch
is the real optimization.
I don't expect there will be much difference in the real world though.
Qu Wenruo (4):
btrfs: integrate the error handling of submit_one_sector()
btrfs: use bitmap_set() to replace set_bit() in a loop
btrfs: extract the io finishing code into a helper
btrfs: reduce extent map lookup during writes
fs/btrfs/extent_io.c | 243 ++++++++++++++++++++++++-------------------
1 file changed, 134 insertions(+), 109 deletions(-)
--
2.52.0
next reply other threads:[~2025-11-20 0:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 0:04 Qu Wenruo [this message]
2025-11-20 0:04 ` [PATCH 1/4] btrfs: integrate the error handling of submit_one_sector() Qu Wenruo
2025-11-20 0:04 ` [PATCH 2/4] btrfs: use bitmap_set() to replace set_bit() in a loop Qu Wenruo
2025-11-20 0:04 ` [PATCH 3/4] btrfs: extract the io finishing code into a helper Qu Wenruo
2025-11-20 0:59 ` Boris Burkov
2025-11-20 1:11 ` Qu Wenruo
2025-11-20 0:04 ` [PATCH 4/4] btrfs: reduce extent map lookup during writes Qu Wenruo
2025-11-20 1:16 ` Boris Burkov
2025-11-20 5:28 ` Qu Wenruo
2025-11-20 9:00 ` Qu Wenruo
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.1763596717.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox