linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikolay Borisov <nborisov@suse.com>
To: Anand Jain <anand.jain@oracle.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: use need_full_stripe() in __btrfs_map_block()
Date: Thu, 12 Oct 2017 12:03:31 +0300	[thread overview]
Message-ID: <ec5ffd06-6881-d121-3046-9a2e1f79993c@suse.com> (raw)
In-Reply-To: <20171012084300.4740-1-anand.jain@oracle.com>



On 12.10.2017 11:43, Anand Jain wrote:
> A cleanup patch, use need_full_stripe() to replace the open code.

The code is equivalent by merit of De Morgan's law (I had to actually go
look up the equivalence classes before I convinced myself it was correct)

~A ^ ~B == ~(A or B)

Reviewed-by: Nikolay Borisov <nborisov@suse.com>



> 
> Signed-off-by: Anand Jain <anand.jain@oracle.com>
> ---
>  fs/btrfs/volumes.c | 16 ++++++----------
>  1 file changed, 6 insertions(+), 10 deletions(-)
> 
> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
> index 3b3ba1ecd88b..f5dee43f8f3f 100644
> --- a/fs/btrfs/volumes.c
> +++ b/fs/btrfs/volumes.c
> @@ -5673,10 +5673,10 @@ static int __btrfs_map_block(struct btrfs_fs_info *fs_info,
>  	if (map->type & BTRFS_BLOCK_GROUP_RAID0) {
>  		stripe_nr = div_u64_rem(stripe_nr, map->num_stripes,
>  				&stripe_index);
> -		if (op != BTRFS_MAP_WRITE && op != BTRFS_MAP_GET_READ_MIRRORS)
> +		if (!need_full_stripe(op))
>  			mirror_num = 1;
>  	} else if (map->type & BTRFS_BLOCK_GROUP_RAID1) {
> -		if (op == BTRFS_MAP_WRITE || op == BTRFS_MAP_GET_READ_MIRRORS)
> +		if (need_full_stripe(op))
>  			num_stripes = map->num_stripes;
>  		else if (mirror_num)
>  			stripe_index = mirror_num - 1;
> @@ -5689,7 +5689,7 @@ static int __btrfs_map_block(struct btrfs_fs_info *fs_info,
>  		}
>  
>  	} else if (map->type & BTRFS_BLOCK_GROUP_DUP) {
> -		if (op == BTRFS_MAP_WRITE || op == BTRFS_MAP_GET_READ_MIRRORS) {
> +		if (need_full_stripe(op)) {
>  			num_stripes = map->num_stripes;
>  		} else if (mirror_num) {
>  			stripe_index = mirror_num - 1;
> @@ -5703,7 +5703,7 @@ static int __btrfs_map_block(struct btrfs_fs_info *fs_info,
>  		stripe_nr = div_u64_rem(stripe_nr, factor, &stripe_index);
>  		stripe_index *= map->sub_stripes;
>  
> -		if (op == BTRFS_MAP_WRITE || op == BTRFS_MAP_GET_READ_MIRRORS)
> +		if (need_full_stripe(op))
>  			num_stripes = map->sub_stripes;
>  		else if (mirror_num)
>  			stripe_index += mirror_num - 1;
> @@ -5718,9 +5718,7 @@ static int __btrfs_map_block(struct btrfs_fs_info *fs_info,
>  		}
>  
>  	} else if (map->type & BTRFS_BLOCK_GROUP_RAID56_MASK) {
> -		if (need_raid_map &&
> -		    (op == BTRFS_MAP_WRITE || op == BTRFS_MAP_GET_READ_MIRRORS ||
> -		     mirror_num > 1)) {
> +		if (need_raid_map && (need_full_stripe(op) || mirror_num > 1)) {
>  			/* push stripe_nr back to the start of the full stripe */
>  			stripe_nr = div64_u64(raid56_full_stripe_start,
>  					stripe_len * nr_data_stripes(map));
> @@ -5747,9 +5745,7 @@ static int __btrfs_map_block(struct btrfs_fs_info *fs_info,
>  			/* We distribute the parity blocks across stripes */
>  			div_u64_rem(stripe_nr + stripe_index, map->num_stripes,
>  					&stripe_index);
> -			if ((op != BTRFS_MAP_WRITE &&
> -			     op != BTRFS_MAP_GET_READ_MIRRORS) &&
> -			    mirror_num <= 1)
> +			if (!need_full_stripe(op) && mirror_num <= 1)
>  				mirror_num = 1;
>  		}
>  	} else {
> 

  parent reply	other threads:[~2017-10-12  9:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-12  8:43 [PATCH] btrfs: use need_full_stripe() in __btrfs_map_block() Anand Jain
2017-10-12  8:51 ` Qu Wenruo
2017-10-12  9:03 ` Nikolay Borisov [this message]
2017-10-16 14:17   ` David Sterba
2017-10-16 14:26     ` Nikolay Borisov

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=ec5ffd06-6881-d121-3046-9a2e1f79993c@suse.com \
    --to=nborisov@suse.com \
    --cc=anand.jain@oracle.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;
as well as URLs for NNTP newsgroup(s).