From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Christoph Hellwig <hch@lst.de>, Chris Mason <clm@fb.com>,
Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 2/2] btrfs: simplify the no-bioc fast path condition in btrfs_map_block
Date: Tue, 27 Jun 2023 14:26:12 +0800 [thread overview]
Message-ID: <bd7dfd7b-4057-4527-2409-30eddf04a889@gmx.com> (raw)
In-Reply-To: <20230627061324.85216-3-hch@lst.de>
On 2023/6/27 14:13, Christoph Hellwig wrote:
> nr_alloc_stripes can't be one if we are writing to a replacement device,
> as it is incremented for that case right above. Remove the duplicate
> checks.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Qu Wenruo <wqu@suse.com>
Thanks,
Qu
> ---
> fs/btrfs/volumes.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
> index 0d386ed44279ce..4907ed9809109d 100644
> --- a/fs/btrfs/volumes.c
> +++ b/fs/btrfs/volumes.c
> @@ -6402,9 +6402,7 @@ int btrfs_map_block(struct btrfs_fs_info *fs_info, enum btrfs_map_op op,
> * I/O context structure.
> */
> if (smap && num_alloc_stripes == 1 &&
> - !((map->type & BTRFS_BLOCK_GROUP_RAID56_MASK) && mirror_num > 1) &&
> - (op == BTRFS_MAP_READ || !dev_replace_is_ongoing ||
> - !dev_replace->tgtdev)) {
> + !((map->type & BTRFS_BLOCK_GROUP_RAID56_MASK) && mirror_num > 1)) {
> set_io_stripe(smap, map, stripe_index, stripe_offset, stripe_nr);
> if (mirror_num_ret)
> *mirror_num_ret = mirror_num;
next prev parent reply other threads:[~2023-06-27 6:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 6:13 btrfs_map_block tidyups Christoph Hellwig
2023-06-27 6:13 ` [PATCH 1/2] btrfs: be a bit more careful when setting mirror_num_ret in btrfs_map_block Christoph Hellwig
2023-06-27 6:23 ` Qu Wenruo
2023-06-27 7:41 ` Johannes Thumshirn
2023-06-27 6:13 ` [PATCH 2/2] btrfs: simplify the no-bioc fast path condition " Christoph Hellwig
2023-06-27 6:26 ` Qu Wenruo [this message]
2023-06-27 7:41 ` Johannes Thumshirn
2023-06-29 16:28 ` btrfs_map_block tidyups 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=bd7dfd7b-4057-4527-2409-30eddf04a889@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=hch@lst.de \
--cc=josef@toxicpanda.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