From: Leo Martins <loemra.dev@gmail.com>
To: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: [PATCH 0/2] btrfs: find_free_extent cleanups
Date: Mon, 22 Sep 2025 18:13:13 -0700 [thread overview]
Message-ID: <cover.1758587352.git.loemra.dev@gmail.com> (raw)
This patch series improves the btrfs extent allocator with both cleanup
and enhanced debugging capabilities.
The first patch removes redundant RAID loop logic that became obsolete
after previous changes ensured allocations only occur from block groups
with matching flags.
The second patch adds comprehensive tracing to find_free_extent() to
improve debugging and performance analysis capabilities.
Testing:
- Ran xfstests btrfs/auto
- Verified trace events output correctly
Leo Martins (2):
btrfs: remove ffe RAID loop
btrfs: add tracing for find_free_extent skip conditions
fs/btrfs/extent-tree.c | 76 +++++++++++++++++-------------------
fs/btrfs/extent-tree.h | 18 +++++++++
include/trace/events/btrfs.h | 65 ++++++++++++++++++++++++++++++
3 files changed, 118 insertions(+), 41 deletions(-)
--
2.47.3
next reply other threads:[~2025-09-23 1:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 1:13 Leo Martins [this message]
2025-09-23 1:13 ` [PATCH 1/2] btrfs: remove ffe RAID loop Leo Martins
2025-09-24 18:54 ` Boris Burkov
2025-09-23 1:13 ` [PATCH 2/2] btrfs: add tracing for find_free_extent skip conditions Leo Martins
2025-09-24 19:14 ` Boris Burkov
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.1758587352.git.loemra.dev@gmail.com \
--to=loemra.dev@gmail.com \
--cc=kernel-team@fb.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;
as well as URLs for NNTP newsgroup(s).