linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org, dsterba@suse.cz
Subject: Re: [PATCH] btrfs: volumes: Remove the meaningless condition of minimal nr_devs when allocating a chunk
Date: Wed, 14 Mar 2018 21:56:55 +0100	[thread overview]
Message-ID: <20180314205655.GT32007@twin.jikos.cz> (raw)
In-Reply-To: <20180131055615.14454-1-wqu@suse.com>

On Wed, Jan 31, 2018 at 01:56:15PM +0800, Qu Wenruo wrote:
> When checking the minimal nr_devs, there is one dead and meaningless
> condition:
> 
> if (ndevs < devs_increment * sub_stripes || ndevs < devs_min) {
>     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> This condition is meaningless, @devs_increment has nothing to do with
> @sub_stripes.
> 
> In fact, in btrfs_raid_array[], profile with sub_stripes larger than 1
> (RAID10) already has the @devs_increment set to 2.
> So no need to multiple it by @sub_stripes.
> 
> And above condition is also dead.
> For RAID10, @devs_increment * @sub_stripes equals 4, which is also the
> @devs_min of RAID10.
> For other profiles, @sub_stripes is always 1, and since @ndevs is
> rounded down to @devs_increment, the condition will always be true.
> 
> Remove the meaningless condition to make later reader wander less.

I think the condition is a leftover from times when we did not have the nice
raid table and the various values were defined in the function.

Reviewed-by: David Sterba <dsterba@suse.com>

> 
> Signed-off-by: Qu Wenruo <wqu@suse.com>
> ---
>  fs/btrfs/volumes.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
> index 215e85e22c8e..cb0a8d27661b 100644
> --- a/fs/btrfs/volumes.c
> +++ b/fs/btrfs/volumes.c
> @@ -4729,7 +4729,7 @@ static int __btrfs_alloc_chunk(struct btrfs_trans_handle *trans,
>  	/* round down to number of usable stripes */
>  	ndevs = round_down(ndevs, devs_increment);
>  
> -	if (ndevs < devs_increment * sub_stripes || ndevs < devs_min) {
> +	if (ndevs < devs_min) {

The redundant condtion is duplicated in the error message a few lines
below:

4840         if (ndevs < devs_min) {
4841                 ret = -ENOSPC;
4842                 if (btrfs_test_opt(info, ENOSPC_DEBUG)) {
4843                         btrfs_debug(info,
4844         "%s: not enough devices with free space: have=%d minimum required=%d",
4845                                     __func__, ndevs, min(devs_min,
4846                                     devs_increment * sub_stripes));
                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^

so I'll remove it as well.

4847                 }
4848                 goto error;
4849         }
>  		ret = -ENOSPC;
>  		goto error;
>  	}

      parent reply	other threads:[~2018-03-14 20:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-31  5:56 [PATCH] btrfs: volumes: Remove the meaningless condition of minimal nr_devs when allocating a chunk Qu Wenruo
2018-01-31  7:35 ` Nikolay Borisov
2018-01-31  8:48   ` Qu Wenruo
2018-03-14 20:56 ` David Sterba [this message]

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=20180314205655.GT32007@twin.jikos.cz \
    --to=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).