linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: Nikolay Borisov <nborisov@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 2/3] btrfs: add helper btrfs_num_devices() to deduce num_devices
Date: Mon, 16 Jul 2018 13:17:14 +0800	[thread overview]
Message-ID: <c91fe391-7e4c-c9d6-380c-64eba711ffe2@oracle.com> (raw)
In-Reply-To: <2ce4bc42-02b8-48b8-aeec-cb60bb39bff5@suse.com>



On 07/13/2018 07:17 PM, Nikolay Borisov wrote:
> 
> 
> On 13.07.2018 14:17, Anand Jain wrote:
>>
>>
>> On 07/12/2018 03:31 PM, Nikolay Borisov wrote:
>>>
>>>
>>> On 10.07.2018 21:22, Anand Jain wrote:
>>>> When the replace is running the fs_devices::num_devices also includes
>>>> the replace device, however in some operations like device delete and
>>>> balance it needs the actual num_devices without the repalce devices, so
>>>> now the function btrfs_num_devices() just provides that.
>>
>>>> Signed-off-by: Anand Jain <anand.jain@oracle.com>
>>>> ---
>>>>    fs/btrfs/volumes.c | 31 +++++++++++++++++--------------
>>>>    1 file changed, 17 insertions(+), 14 deletions(-)
>>>>
>>>> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
>>>> index ce6faeb8bcf8..59a6d8f42c98 100644
>>>> --- a/fs/btrfs/volumes.c
>>>> +++ b/fs/btrfs/volumes.c
>>>> @@ -1931,6 +1931,20 @@ void btrfs_assign_next_active_device(struct
>>>> btrfs_fs_info *fs_info,
>>>>            fs_info->fs_devices->latest_bdev = next_device->bdev;
>>>>    }
>>>>    
>>>
>>> Put a comment above the function saying it returns the number of devices
>>> minus the replace device (in case replace is working) otherwise one have
>>> to go and 'git blame' it
>>
>> good idea will rename it to btrfs_num_devices_minus_replace(), (will
>> wait to see if there is any better suggested).
> 
> Unfortunately I don't have a better name yet but
> num_devices_minus_replace is way too verbose so don't use that...

  Ok will just add comment. The function name will remain as
  btrfs_num_devices()

Thanks, Anand

>>
>> Thanks, Anand
>>
>>
>>
>>>> +static inline u64 btrfs_num_devices(struct btrfs_fs_info *fs_info)
>>>> +{
>>>> +    u64 num_devices = fs_info->fs_devices->num_devices;
>>>> +
>>>> +    btrfs_dev_replace_read_lock(&fs_info->dev_replace);
>>>> +    if (btrfs_dev_replace_is_ongoing(&fs_info->dev_replace)) {
>>>> +        WARN_ON(num_devices < 1);
>>>> +        num_devices--;
>>>> +    }
>>>> +    btrfs_dev_replace_read_unlock(&fs_info->dev_replace);
>>>> +
>>>> +    return num_devices;
>>>> +}
>>>> +
>>>>    int btrfs_rm_device(struct btrfs_fs_info *fs_info, const char
>>>> *device_path,
>>>>            u64 devid)
>>>>    {
>>>> @@ -1944,13 +1958,7 @@ int btrfs_rm_device(struct btrfs_fs_info
>>>> *fs_info, const char *device_path,
>>>>          mutex_lock(&uuid_mutex);
>>>>    -    num_devices = fs_devices->num_devices;
>>>> -    btrfs_dev_replace_read_lock(&fs_info->dev_replace);
>>>> -    if (btrfs_dev_replace_is_ongoing(&fs_info->dev_replace)) {
>>>> -        WARN_ON(num_devices < 1);
>>>> -        num_devices--;
>>>> -    }
>>>> -    btrfs_dev_replace_read_unlock(&fs_info->dev_replace);
>>>> +    num_devices = btrfs_num_devices(fs_info);
>>>>          ret = btrfs_check_raid_min_devices(fs_info, num_devices - 1);
>>>>        if (ret)
>>>> @@ -3810,13 +3818,8 @@ int btrfs_balance(struct btrfs_fs_info *fs_info,
>>>>            }
>>>>        }
>>>>    -    num_devices = fs_info->fs_devices->num_devices;
>>>> -    btrfs_dev_replace_read_lock(&fs_info->dev_replace);
>>>> -    if (btrfs_dev_replace_is_ongoing(&fs_info->dev_replace)) {
>>>> -        WARN_ON(num_devices < 1);
>>>> -        num_devices--;
>>>> -    }
>>>> -    btrfs_dev_replace_read_unlock(&fs_info->dev_replace);
>>>> +    num_devices = btrfs_num_devices(fs_info);
>>>> +
>>>>        allowed = BTRFS_AVAIL_ALLOC_BIT_SINGLE | BTRFS_BLOCK_GROUP_DUP;
>>>>        if (num_devices > 1)
>>>>            allowed |= (BTRFS_BLOCK_GROUP_RAID0 |
>>>> BTRFS_BLOCK_GROUP_RAID1);
>>>>
>>> -- 
>>> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>
>> -- 
>> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

  reply	other threads:[~2018-07-16  5:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-10 18:22 [PATCH 1/3] btrfs: warn for num_devices below 0 Anand Jain
2018-07-10 18:22 ` [PATCH 2/3] btrfs: add helper btrfs_num_devices() to deduce num_devices Anand Jain
2018-07-12  7:31   ` Nikolay Borisov
2018-07-13 11:17     ` Anand Jain
2018-07-13 11:17       ` Nikolay Borisov
2018-07-16  5:17         ` Anand Jain [this message]
2018-07-10 18:22 ` [PATCH 3/3] btrfs: add helper function check device delete able Anand Jain
2018-07-12  7:43   ` Nikolay Borisov
2018-07-13 11:27     ` Anand Jain
2018-07-13 11:28       ` Nikolay Borisov
2018-07-16  5:14         ` Anand Jain
2018-07-12  7:13 ` [PATCH 1/3] btrfs: warn for num_devices below 0 Nikolay Borisov
2018-07-13 11:05   ` Anand Jain

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=c91fe391-7e4c-c9d6-380c-64eba711ffe2@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=nborisov@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).