From: David Sterba <dsterba@suse.cz>
To: fdmanana@kernel.org
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/4] btrfs: fix inefficiencies when reading extent buffers and some cleanups
Date: Mon, 14 Mar 2022 14:07:56 +0100 [thread overview]
Message-ID: <20220314130756.GI12643@twin.jikos.cz> (raw)
In-Reply-To: <cover.1646998177.git.fdmanana@suse.com>
On Fri, Mar 11, 2022 at 11:35:30AM +0000, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
>
> Fix a couple inefficiencies when reading an extent buffer while searching
> a btree plus a couple cleanups in the same area. Spotted while working on
> other stuff, but this is separate and independent enough to be in its own
> small patchset.
>
> Filipe Manana (4):
> btrfs: avoid unnecessary btree search restarts when reading node
> btrfs: release upper nodes when reading stale btree node from disk
> btrfs: update outdated comment for read_block_for_search()
> btrfs: remove trivial wrapper btrfs_read_buffer()
Added to misc-next, thanks.
prev parent reply other threads:[~2022-03-14 13:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 11:35 [PATCH 0/4] btrfs: fix inefficiencies when reading extent buffers and some cleanups fdmanana
2022-03-11 11:35 ` [PATCH 1/4] btrfs: avoid unnecessary btree search restarts when reading node fdmanana
2022-03-11 11:35 ` [PATCH 2/4] btrfs: release upper nodes when reading stale btree node from disk fdmanana
2022-03-11 11:35 ` [PATCH 3/4] btrfs: update outdated comment for read_block_for_search() fdmanana
2022-03-11 11:35 ` [PATCH 4/4] btrfs: remove trivial wrapper btrfs_read_buffer() fdmanana
2022-03-11 16:14 ` [PATCH 0/4] btrfs: fix inefficiencies when reading extent buffers and some cleanups Josef Bacik
2022-03-14 13:07 ` 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=20220314130756.GI12643@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