Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Josef Bacik <josef@toxicpanda.com>,
	linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH 01/15] btrfs: don't do find_extent_buffer in do_walk_down
Date: Wed, 24 Apr 2024 07:25:11 +0930	[thread overview]
Message-ID: <79a004f4-952c-4382-ad75-e1b669df5ddc@gmx.com> (raw)
In-Reply-To: <c30d22dcf2f6418a803ea2e0066545566829afa1.1713550368.git.josef@toxicpanda.com>



在 2024/4/20 03:46, Josef Bacik 写道:
> We do find_extent_buffer(), and then if we don't find the eb in cache we
> call btrfs_find_create_tree_block(), which calls find_extent_buffer()
> first and then allocates the extent buffer.
>
> The reason we're doing this is because if we don't find the extent
> buffer in cache we set reada = 1.  However this doesn't matter, because
> lower down we only trigger reada if !btrfs_buffer_uptodate(eb), which is
> what the case would be if we didn't find the extent buffer in cache and
> had to allocate it.
>
> Clean this up to simply call btrfs_find_create_tree_block(), and then
> use the fact that we're having to read the extent buffer off of disk to
> go ahead and kick off readahead.
>
> Signed-off-by: Josef Bacik <josef@toxicpanda.com>

Reviewed-by: Qu Wenruo <wqu@suse.com>

Thanks,
Qu
> ---
>   fs/btrfs/extent-tree.c | 16 ++++++----------
>   1 file changed, 6 insertions(+), 10 deletions(-)
>
> diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c
> index 023920d0d971..64bb8c69e57a 100644
> --- a/fs/btrfs/extent-tree.c
> +++ b/fs/btrfs/extent-tree.c
> @@ -5434,7 +5434,6 @@ static noinline int do_walk_down(struct btrfs_trans_handle *trans,
>   	struct btrfs_key key;
>   	struct extent_buffer *next;
>   	int level = wc->level;
> -	int reada = 0;
>   	int ret = 0;
>   	bool need_account = false;
>
> @@ -5460,14 +5459,11 @@ static noinline int do_walk_down(struct btrfs_trans_handle *trans,
>   	btrfs_node_key_to_cpu(path->nodes[level], &check.first_key,
>   			      path->slots[level]);
>
> -	next = find_extent_buffer(fs_info, bytenr);
> -	if (!next) {
> -		next = btrfs_find_create_tree_block(fs_info, bytenr,
> -				btrfs_root_id(root), level - 1);
> -		if (IS_ERR(next))
> -			return PTR_ERR(next);
> -		reada = 1;
> -	}
> +	next = btrfs_find_create_tree_block(fs_info, bytenr,
> +					    btrfs_root_id(root), level - 1);
> +	if (IS_ERR(next))
> +		return PTR_ERR(next);
> +
>   	btrfs_tree_lock(next);
>
>   	ret = btrfs_lookup_extent_info(trans, fs_info, bytenr, level - 1, 1,
> @@ -5518,7 +5514,7 @@ static noinline int do_walk_down(struct btrfs_trans_handle *trans,
>   	}
>
>   	if (!next) {
> -		if (reada && level == 1)
> +		if (level == 1)
>   			reada_walk_down(trans, root, wc, path);
>   		next = read_tree_block(fs_info, bytenr, &check);
>   		if (IS_ERR(next)) {

  reply	other threads:[~2024-04-23 21:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-19 18:16 [PATCH 00/15] btrfs: snapshot delete cleanups Josef Bacik
2024-04-19 18:16 ` [PATCH 01/15] btrfs: don't do find_extent_buffer in do_walk_down Josef Bacik
2024-04-23 21:55   ` Qu Wenruo [this message]
2024-04-19 18:16 ` [PATCH 02/15] btrfs: push ->owner_root check into btrfs_read_extent_buffer Josef Bacik
2024-04-23 22:09   ` Qu Wenruo
2024-04-19 18:16 ` [PATCH 03/15] btrfs: use btrfs_read_extent_buffer in do_walk_down Josef Bacik
2024-04-19 18:16 ` [PATCH 04/15] btrfs: push lookup_info into walk_control Josef Bacik
2024-04-19 18:17 ` [PATCH 05/15] btrfs: move the eb uptodate code into it's own helper Josef Bacik
2024-04-19 18:17 ` [PATCH 06/15] btrfs: remove need_account in do_walk_down Josef Bacik
2024-04-19 18:17 ` [PATCH 07/15] btrfs: unify logic to decide if we need to walk down into a node Josef Bacik
2024-04-19 18:17 ` [PATCH 08/15] btrfs: extract the reference dropping code into it's own helper Josef Bacik
2024-04-19 18:17 ` [PATCH 09/15] btrfs: don't BUG_ON ENOMEM in walk_down_proc Josef Bacik
2024-04-19 18:17 ` [PATCH 10/15] btrfs: handle errors from ref mods during UPDATE_BACKREF Josef Bacik
2024-04-19 18:17 ` [PATCH 11/15] btrfs: replace BUG_ON with ASSERT in walk_down_proc Josef Bacik
2024-04-19 18:17 ` [PATCH 12/15] btrfs: clean up our handling of refs == 0 in snapshot delete Josef Bacik
2024-04-24 12:23   ` David Sterba
2024-04-19 18:17 ` [PATCH 13/15] btrfs: convert correctness BUG_ON()'s to ASSERT()'s in walk_up_proc Josef Bacik
2024-04-19 18:17 ` [PATCH 14/15] btrfs: handle errors from btrfs_dec_ref properly Josef Bacik
2024-04-19 18:17 ` [PATCH 15/15] btrfs: add documentation around snapshot delete Josef Bacik
2024-04-24 12:31 ` [PATCH 00/15] btrfs: snapshot delete 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=79a004f4-952c-4382-ad75-e1b669df5ddc@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=josef@toxicpanda.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