From: David Sterba <dsterba@suse.cz>
To: fdmanana@kernel.org
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 00/11] btrfs: some optimizations and cleanups for io trees
Date: Wed, 18 Mar 2026 12:02:41 +0100 [thread overview]
Message-ID: <20260318110241.GC5735@twin.jikos.cz> (raw)
In-Reply-To: <cover.1773676775.git.fdmanana@suse.com>
On Mon, Mar 16, 2026 at 04:14:03PM +0000, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
>
> An assorted set of optimizations and cleanups for io trees. The last patch
> contains some benchmark results after applying the whole patchset.
>
> Filipe Manana (11):
> btrfs: optimize clearing all bits from the last extent record in an io tree
> btrfs: turn extent_io_tree_panic() into a macro for better error reporting
> btrfs: tag as unlikely branches that call extent_io_tree_panic()
> btrfs: make add_extent_changeset() only return errors or success
> btrfs: use extent_io_tree_panic() instead of BUG_ON()
> btrfs: change last argument of add_extent_changeset() to boolean
> btrfs: remove wake parameter from clear_state_bit()
> btrfs: avoid unnecessary wake ups on io trees when there are no waiters
> btrfs: free cached state outside critical section in wait_extent_bit()
> btrfs: panic instead of warn when splitting extent state not in the tree
> btrfs: optimize clearing all bits from first extent record in an io tree
Reviewed-by: David Sterba <dsterba@suse.com>
prev parent reply other threads:[~2026-03-18 11:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 16:14 [PATCH 00/11] btrfs: some optimizations and cleanups for io trees fdmanana
2026-03-16 16:14 ` [PATCH 01/11] btrfs: optimize clearing all bits from the last extent record in an io tree fdmanana
2026-03-16 16:14 ` [PATCH 02/11] btrfs: turn extent_io_tree_panic() into a macro for better error reporting fdmanana
2026-03-16 16:14 ` [PATCH 03/11] btrfs: tag as unlikely branches that call extent_io_tree_panic() fdmanana
2026-03-16 16:14 ` [PATCH 04/11] btrfs: make add_extent_changeset() only return errors or success fdmanana
2026-03-16 16:14 ` [PATCH 05/11] btrfs: use extent_io_tree_panic() instead of BUG_ON() fdmanana
2026-03-16 16:14 ` [PATCH 06/11] btrfs: change last argument of add_extent_changeset() to boolean fdmanana
2026-03-16 16:14 ` [PATCH 07/11] btrfs: remove wake parameter from clear_state_bit() fdmanana
2026-03-16 16:14 ` [PATCH 08/11] btrfs: avoid unnecessary wake ups on io trees when there are no waiters fdmanana
2026-03-16 16:14 ` [PATCH 09/11] btrfs: free cached state outside critical section in wait_extent_bit() fdmanana
2026-03-16 16:14 ` [PATCH 10/11] btrfs: panic instead of warn when splitting extent state not in the tree fdmanana
2026-03-16 16:14 ` [PATCH 11/11] btrfs: optimize clearing all bits from first extent record in an io tree fdmanana
2026-03-18 11:02 ` David Sterba [this message]
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=20260318110241.GC5735@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=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