mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: "hch@infradead.org" <hch@infradead.org>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
	David Sterba <dsterba@suse.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 11/13] btrfs: open code set_io_stripe for RAID56
Date: Wed, 13 Dec 2023 15:36:23 +0000	[thread overview]
Message-ID: <3719a73b-aef3-47e4-92c3-ec055e8bde9d@wdc.com> (raw)
In-Reply-To: <ZXlyPqtXO+j90vJb@infradead.org>

On 13.12.23 09:58, Christoph Hellwig wrote:
> 
> I think raid stripe tree handling also really should move out of
> set_io_stripe.  Below is the latest I have, although it probably won't
> apply to your tree:

I've decided to add that one afterwards giving the attribution to you.
There are some other patches in your tree as well, which I want to have 
a look at too.

> ---
>  From ac208da48d7f9d11eef8a01ac0c6fbf9681665b5 Mon Sep 17 00:00:00 2001
> From: Christoph Hellwig <hch@lst.de>
> Date: Thu, 22 Jun 2023 05:53:13 +0200
> Subject: btrfs: move raid-stripe-tree handling out of set_io_stripe
> 
> set_io_stripe gets a little too complicated with the raid-stripe-tree
> handling.  Move it out into the only callers that actually needs it.
> 
> The only reads with more than a single stripe is the parity raid recovery
> case thast will need very special handling anyway once implemented.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
>   fs/btrfs/volumes.c | 61 ++++++++++++++++++++--------------------------
>   1 file changed, 27 insertions(+), 34 deletions(-)
> 
> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
> index 30ee5d1670d034..e32eefa242b0a4 100644
> --- a/fs/btrfs/volumes.c
> +++ b/fs/btrfs/volumes.c
> @@ -6233,22 +6233,12 @@ static u64 btrfs_max_io_len(struct map_lookup *map, enum btrfs_map_op op,
>   	return U64_MAX;
>   }
>   
> -static int set_io_stripe(struct btrfs_fs_info *fs_info, enum btrfs_map_op op,
> -		      u64 logical, u64 *length, struct btrfs_io_stripe *dst,
> -		      struct map_lookup *map, u32 stripe_index,
> -		      u64 stripe_offset, u64 stripe_nr)
> +static void set_io_stripe(struct btrfs_io_stripe *dst, const struct map_lookup *map,
> +			  u32 stripe_index, u64 stripe_offset, u32 stripe_nr)
>   {
>   	dst->dev = map->stripes[stripe_index].dev;
> -
> -	if (op == BTRFS_MAP_READ &&
> -	    btrfs_use_raid_stripe_tree(fs_info, map->type))
> -		return btrfs_get_raid_extent_offset(fs_info, logical, length,
> -						    map->type, stripe_index,
> -						    dst);
> -
>   	dst->physical = map->stripes[stripe_index].physical +
>   			stripe_offset + ((u64)stripe_nr << BTRFS_STRIPE_LEN_SHIFT);
> -	return 0;
>   }
>   
>   int btrfs_map_block(struct btrfs_fs_info *fs_info, enum btrfs_map_op op,
> @@ -6423,15 +6413,24 @@ int btrfs_map_block(struct btrfs_fs_info *fs_info, enum btrfs_map_op op,
>   	 * physical block information on the stack instead of allocating an
>   	 * I/O context structure.
>   	 */
> -	if (smap && num_alloc_stripes == 1 &&
> -	    !(btrfs_use_raid_stripe_tree(fs_info, map->type) &&
> -	      op != BTRFS_MAP_READ) &&
> -	    !((map->type & BTRFS_BLOCK_GROUP_RAID56_MASK) && mirror_num > 1)) {
> -		ret = set_io_stripe(fs_info, op, logical, length, smap, map,
> -				    stripe_index, stripe_offset, stripe_nr);
> -		*mirror_num_ret = mirror_num;
> -		*bioc_ret = NULL;
> -		goto out;
> +	if (smap && num_alloc_stripes == 1) {
> +		if (op == BTRFS_MAP_READ &&
> +		    btrfs_use_raid_stripe_tree(fs_info, map->type)) {
> +			ret = btrfs_get_raid_extent_offset(fs_info, logical,
> +							   length, map->type,
> +							   stripe_index, smap);
> +			*mirror_num_ret = mirror_num;
> +			*bioc_ret = NULL;
> +			goto out;
> +		} else if (!(map->type & BTRFS_BLOCK_GROUP_RAID56_MASK) ||
> +			   mirror_num == 0) {
> +			set_io_stripe(smap, map, stripe_index, stripe_offset,
> +				      stripe_nr);
> +			*mirror_num_ret = mirror_num;
> +			*bioc_ret = NULL;
> +			ret = 0;
> +			goto out;
> +		}
>   	}
>   
>   	bioc = alloc_btrfs_io_context(fs_info, logical, num_alloc_stripes);
> @@ -6448,6 +6447,8 @@ int btrfs_map_block(struct btrfs_fs_info *fs_info, enum btrfs_map_op op,
>   	 *
>   	 * It's still mostly the same as other profiles, just with extra rotation.
>   	 */
> +	ASSERT(op != BTRFS_MAP_READ ||
> +	       btrfs_use_raid_stripe_tree(fs_info, map->type));
>   	if (map->type & BTRFS_BLOCK_GROUP_RAID56_MASK && need_raid_map &&
>   	    (op != BTRFS_MAP_READ || mirror_num > 1)) {
>   		/*
> @@ -6461,29 +6462,21 @@ int btrfs_map_block(struct btrfs_fs_info *fs_info, enum btrfs_map_op op,
>   		bioc->full_stripe_logical = em->start +
>   			((stripe_nr * data_stripes) << BTRFS_STRIPE_LEN_SHIFT);
>   		for (i = 0; i < num_stripes; i++)
> -			ret = set_io_stripe(fs_info, op, logical, length,
> -					    &bioc->stripes[i], map,
> -					    (i + stripe_nr) % num_stripes,
> -					    stripe_offset, stripe_nr);
> +			set_io_stripe(&bioc->stripes[i], map,
> +				      (i + stripe_nr) % num_stripes,
> +				      stripe_offset, stripe_nr);
>   	} else {
>   		/*
>   		 * For all other non-RAID56 profiles, just copy the target
>   		 * stripe into the bioc.
>   		 */
>   		for (i = 0; i < num_stripes; i++) {
> -			ret = set_io_stripe(fs_info, op, logical, length,
> -					    &bioc->stripes[i], map, stripe_index,
> -					    stripe_offset, stripe_nr);
> +			set_io_stripe(&bioc->stripes[i], map, stripe_index,
> +				      stripe_offset, stripe_nr);
>   			stripe_index++;
>   		}
>   	}
>   
> -	if (ret) {
> -		*bioc_ret = NULL;
> -		btrfs_put_bioc(bioc);
> -		goto out;
> -	}
> -
>   	if (op != BTRFS_MAP_READ)
>   		max_errors = btrfs_chunk_max_errors(map);
>   


  parent reply	other threads:[~2023-12-13 15:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-12 12:37 [PATCH 00/13] btrfs: clean up RAID I/O geometry calculation Johannes Thumshirn
2023-12-12 12:37 ` [PATCH 01/13] btrfs: factor out helper for single device IO check Johannes Thumshirn
2023-12-13  8:49   ` Christoph Hellwig
2023-12-12 12:38 ` [PATCH 02/13] btrfs: re-introduce struct btrfs_io_geometry Johannes Thumshirn
2023-12-12 12:38 ` [PATCH 03/13] btrfs: factor out block-mapping for RAID0 Johannes Thumshirn
2023-12-13  8:50   ` Christoph Hellwig
2023-12-13  9:02     ` Johannes Thumshirn
2023-12-12 12:38 ` [PATCH 04/13] btrfs: factor out RAID1 block mapping Johannes Thumshirn
2023-12-13  8:52   ` Christoph Hellwig
2023-12-12 12:38 ` [PATCH 05/13] btrfs: factor out block mapping for DUP profiles Johannes Thumshirn
2023-12-12 12:38 ` [PATCH 06/13] btrfs: factor out block mapping for RAID10 Johannes Thumshirn
2023-12-12 12:38 ` [PATCH 07/13] btrfs: reduce scope of data_stripes in btrfs_map_block Johannes Thumshirn
2023-12-12 12:38 ` [PATCH 08/13] btrfs: factor out block mapping for RAID5/6 Johannes Thumshirn
2023-12-13  8:53   ` Christoph Hellwig
2023-12-13  9:04     ` Johannes Thumshirn
2023-12-12 12:38 ` [PATCH 09/13] btrfs: factor out block mapping for single profiles Johannes Thumshirn
2023-12-12 12:38 ` [PATCH 10/13] btrfs: untagle if else maze in btrfs_map_block Johannes Thumshirn
2023-12-13  8:53   ` Christoph Hellwig
2023-12-12 12:38 ` [PATCH 11/13] btrfs: open code set_io_stripe for RAID56 Johannes Thumshirn
2023-12-13  8:58   ` Christoph Hellwig
2023-12-13  9:09     ` Johannes Thumshirn
2023-12-13  9:17       ` hch
2023-12-13  9:23         ` Johannes Thumshirn
2023-12-13 15:36     ` Johannes Thumshirn [this message]
2023-12-12 12:38 ` [PATCH 12/13] btrfs: pass struct btrfs_io_geometry to set_io_stripe Johannes Thumshirn
2023-12-12 12:38 ` [PATCH 13/13] btrfs: pass btrfs_io_geometry into btrfs_max_io_len Johannes Thumshirn

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=3719a73b-aef3-47e4-92c3-ec055e8bde9d@wdc.com \
    --to=johannes.thumshirn@wdc.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=hch@infradead.org \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®