linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikolay Borisov <nborisov@suse.com>
To: Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org, dsterba@suse.cz
Subject: Re: [PATCH] btrfs: volumes: Cleanup stripe size calculation
Date: Wed, 31 Jan 2018 09:36:41 +0200	[thread overview]
Message-ID: <02241cf3-1577-df10-faf2-b201320cd668@suse.com> (raw)
In-Reply-To: <20180131061634.17383-1-wqu@suse.com>



On 31.01.2018 08:16, Qu Wenruo wrote:
> Cleanup the following things:
> 1) open coded SZ_16M round up
> 2) use min() to replace open-coded size comparison
> 3) code style
> 
> Signed-off-by: Qu Wenruo <wqu@suse.com>

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

> ---
>  fs/btrfs/volumes.c | 11 +++++------
>  1 file changed, 5 insertions(+), 6 deletions(-)
> 
> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
> index cb0a8d27661b..90ad716d2b50 100644
> --- a/fs/btrfs/volumes.c
> +++ b/fs/btrfs/volumes.c
> @@ -4761,18 +4761,17 @@ static int __btrfs_alloc_chunk(struct btrfs_trans_handle *trans,
>  	 * and compare that answer with the max chunk size
>  	 */
>  	if (stripe_size * data_stripes > max_chunk_size) {
> -		u64 mask = (1ULL << 24) - 1;
> -
>  		stripe_size = div_u64(max_chunk_size, data_stripes);
>  
>  		/* bump the answer up to a 16MB boundary */
> -		stripe_size = (stripe_size + mask) & ~mask;
> +		stripe_size = round_up(stripe_size, SZ_16M);
>  
> -		/* but don't go higher than the limits we found
> +		/*
> +		 * but don't go higher than the limits we found
>  		 * while searching for free extents
>  		 */
> -		if (stripe_size > devices_info[ndevs-1].max_avail)
> -			stripe_size = devices_info[ndevs-1].max_avail;
> +		stripe_size = min(devices_info[ndevs - 1].max_avail,
> +				  stripe_size);
>  	}
>  
>  	stripe_size = div_u64(stripe_size, dev_stripes);
> 

  reply	other threads:[~2018-01-31  7:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-31  6:16 [PATCH] btrfs: volumes: Cleanup stripe size calculation Qu Wenruo
2018-01-31  7:36 ` Nikolay Borisov [this message]
2018-01-31  8:34 ` Gu, Jinxiang
2018-01-31 15:07 ` 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=02241cf3-1577-df10-faf2-b201320cd668@suse.com \
    --to=nborisov@suse.com \
    --cc=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wqu@suse.com \
    /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).