From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 00/22] btrfs: some io tree optimizations and cleanups
Date: Wed, 23 Apr 2025 15:19:40 +0100 [thread overview]
Message-ID: <cover.1745401627.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
An assorted set of optimizations and cleanups related to io trees.
Details in the change logs.
Filipe Manana (22):
btrfs: remove duplicate error check at btrfs_clear_extent_bit_changeset()
btrfs: exit after state split error at btrfs_clear_extent_bit_changeset()
btrfs: add missing error return to btrfs_clear_extent_bit_changeset()
btrfs: use bools for local variables at btrfs_clear_extent_bit_changeset()
btrfs: avoid extra tree search at btrfs_clear_extent_bit_changeset()
btrfs: simplify last record detection at btrfs_clear_extent_bit_changeset()
btrfs: remove duplicate error check at btrfs_convert_extent_bit()
btrfs: exit after state split error at btrfs_convert_extent_bit()
btrfs: exit after state insertion failure at btrfs_convert_extent_bit()
btrfs: avoid unnecessary next node searches when clearing bits from extent range
btrfs: avoid repeated extent state processing when converting extent bits
btrfs: avoid researching tree when converting bits in an extent range
btrfs: simplify last record detection at btrfs_convert_extent_bit()
btrfs: exit after state insertion failure at set_extent_bit()
btrfs: exit after state split error at set_extent_bit()
btrfs: simplify last record detection at set_extent_bit()
btrfs: avoid repeated extent state processing when setting extent bits
btrfs: avoid researching tree when setting bits in an extent range
btrfs: remove unnecessary NULL checks before freeing extent state
btrfs: don't BUG_ON() when unpinning extents during transaction commit
btrfs: remove variable to track trimmed bytes at btrfs_finish_extent_commit()
btrfs: make extent unpinning more efficient when committing transaction
fs/btrfs/extent-io-tree.c | 215 +++++++++++++++++++++++++-------------
fs/btrfs/extent-io-tree.h | 3 +
fs/btrfs/extent-tree.c | 68 ++++++++----
fs/btrfs/transaction.c | 4 +-
4 files changed, 195 insertions(+), 95 deletions(-)
--
2.47.2
next reply other threads:[~2025-04-23 14:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 14:19 fdmanana [this message]
2025-04-23 14:19 ` [PATCH 01/22] btrfs: remove duplicate error check at btrfs_clear_extent_bit_changeset() fdmanana
2025-04-23 14:19 ` [PATCH 02/22] btrfs: exit after state split error " fdmanana
2025-04-23 14:19 ` [PATCH 03/22] btrfs: add missing error return to btrfs_clear_extent_bit_changeset() fdmanana
2025-04-23 14:19 ` [PATCH 04/22] btrfs: use bools for local variables at btrfs_clear_extent_bit_changeset() fdmanana
2025-04-23 14:19 ` [PATCH 05/22] btrfs: avoid extra tree search " fdmanana
2025-04-23 14:19 ` [PATCH 06/22] btrfs: simplify last record detection " fdmanana
2025-04-23 14:19 ` [PATCH 07/22] btrfs: remove duplicate error check at btrfs_convert_extent_bit() fdmanana
2025-04-23 14:19 ` [PATCH 08/22] btrfs: exit after state split error " fdmanana
2025-04-23 14:19 ` [PATCH 09/22] btrfs: exit after state insertion failure " fdmanana
2025-04-23 14:19 ` [PATCH 10/22] btrfs: avoid unnecessary next node searches when clearing bits from extent range fdmanana
2025-04-23 14:19 ` [PATCH 11/22] btrfs: avoid repeated extent state processing when converting extent bits fdmanana
2025-04-23 14:19 ` [PATCH 12/22] btrfs: avoid researching tree when converting bits in an extent range fdmanana
2025-04-23 14:19 ` [PATCH 13/22] btrfs: simplify last record detection at btrfs_convert_extent_bit() fdmanana
2025-04-23 14:19 ` [PATCH 14/22] btrfs: exit after state insertion failure at set_extent_bit() fdmanana
2025-04-23 14:19 ` [PATCH 15/22] btrfs: exit after state split error " fdmanana
2025-04-23 14:19 ` [PATCH 16/22] btrfs: simplify last record detection " fdmanana
2025-04-23 14:19 ` [PATCH 17/22] btrfs: avoid repeated extent state processing when setting extent bits fdmanana
2025-04-23 14:19 ` [PATCH 18/22] btrfs: avoid researching tree when setting bits in an extent range fdmanana
2025-04-23 14:19 ` [PATCH 19/22] btrfs: remove unnecessary NULL checks before freeing extent state fdmanana
2025-04-23 14:20 ` [PATCH 20/22] btrfs: don't BUG_ON() when unpinning extents during transaction commit fdmanana
2025-04-23 14:20 ` [PATCH 21/22] btrfs: remove variable to track trimmed bytes at btrfs_finish_extent_commit() fdmanana
2025-04-23 14:20 ` [PATCH 22/22] btrfs: make extent unpinning more efficient when committing transaction fdmanana
2025-04-28 14:53 ` [PATCH 00/22] btrfs: some io tree optimizations and cleanups 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.1745401627.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