From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>
Subject: [PATCH 0/2] Backref iterator size reduction
Date: Thu, 30 Apr 2026 17:24:59 +0200 [thread overview]
Message-ID: <cover.1777561536.git.dsterba@suse.com> (raw)
Remove fs_info from struct btrfs_backref_iter and replace allocation by
on-stack usage.
David Sterba (2):
btrfs: remove fs_info from struct btrfs_backref_iter
btrfs: use on stack backref iterator in build_backref_tree()
fs/btrfs/backref.c | 39 ++++++++++++++-------------------------
fs/btrfs/backref.h | 9 ++++-----
fs/btrfs/relocation.c | 13 ++++++-------
3 files changed, 24 insertions(+), 37 deletions(-)
--
2.53.0
next reply other threads:[~2026-04-30 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 15:24 David Sterba [this message]
2026-04-30 15:25 ` [PATCH 1/2] btrfs: remove fs_info from struct btrfs_backref_iter David Sterba
2026-04-30 15:25 ` [PATCH 2/2] btrfs: use on stack backref iterator in build_backref_tree() 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.1777561536.git.dsterba@suse.com \
--to=dsterba@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.