All of lore.kernel.org
 help / color / mirror / Atom feed
From: Damien Le Moal <Damien.LeMoal@wdc.com>
To: Anand Jain <anand.jain@oracle.com>,
	"dsterba@suse.cz" <dsterba@suse.cz>,
	Naohiro Aota <Naohiro.Aota@wdc.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
	"dsterba@suse.com" <dsterba@suse.com>,
	"hare@suse.com" <hare@suse.com>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	Jens Axboe <axboe@kernel.dk>,
	"hch@infradead.org" <hch@infradead.org>,
	"Darrick J. Wong" <darrick.wong@oracle.com>,
	Johannes Thumshirn <Johannes.Thumshirn@wdc.com>,
	Josef Bacik <josef@toxicpanda.com>
Subject: Re: [PATCH v10 05/41] btrfs: check and enable ZONED mode
Date: Tue, 1 Dec 2020 06:09:27 +0000	[thread overview]
Message-ID: <CH2PR04MB652224DE2A682FADE28F443DE7F40@CH2PR04MB6522.namprd04.prod.outlook.com> (raw)
In-Reply-To: 47fffa8d-a495-5588-f970-1ab04ece19b6@oracle.com

On 2020/12/01 14:54, Anand Jain wrote:
> On 1/12/20 10:29 am, Damien Le Moal wrote:
>> On 2020/12/01 11:20, Anand Jain wrote:
>>> On 30/11/20 9:15 pm, Damien Le Moal wrote:
>>>> On 2020/11/30 21:13, Anand Jain wrote:
>>>>> On 28/11/20 2:44 am, David Sterba wrote:
>>>>>> On Wed, Nov 18, 2020 at 07:29:20PM +0800, Anand Jain wrote:
>>>>>>> On 10/11/20 7:26 pm, Naohiro Aota wrote:
>>>>>>>> This commit introduces the function btrfs_check_zoned_mode() to check if
>>>>>>>> ZONED flag is enabled on the file system and if the file system consists of
>>>>>>>> zoned devices with equal zone size.
>>>>>>>>
>>>>>>>> Signed-off-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
>>>>>>>> Signed-off-by: Damien Le Moal <damien.lemoal@wdc.com>
>>>>>>>> Signed-off-by: Naohiro Aota <naohiro.aota@wdc.com>
>>>>>>>> Reviewed-by: Josef Bacik <josef@toxicpanda.com>
>>>>>>>> ---
>>>>>>>>      fs/btrfs/ctree.h       | 11 ++++++
>>>>>>>>      fs/btrfs/dev-replace.c |  7 ++++
>>>>>>>>      fs/btrfs/disk-io.c     | 11 ++++++
>>>>>>>>      fs/btrfs/super.c       |  1 +
>>>>>>>>      fs/btrfs/volumes.c     |  5 +++
>>>>>>>>      fs/btrfs/zoned.c       | 81 ++++++++++++++++++++++++++++++++++++++++++
>>>>>>>>      fs/btrfs/zoned.h       | 26 ++++++++++++++
>>>>>>>>      7 files changed, 142 insertions(+)
>>>>>>>>
>>>>>>>> diff --git a/fs/btrfs/ctree.h b/fs/btrfs/ctree.h
>>>>>>>> index aac3d6f4e35b..453f41ca024e 100644
>>>>>>>> --- a/fs/btrfs/ctree.h
>>>>>>>> +++ b/fs/btrfs/ctree.h
>>>>>>>> @@ -948,6 +948,12 @@ struct btrfs_fs_info {
>>>>>>>>      	/* Type of exclusive operation running */
>>>>>>>>      	unsigned long exclusive_operation;
>>>>>>>>      
>>>>>>>> +	/* Zone size when in ZONED mode */
>>>>>>>> +	union {
>>>>>>>> +		u64 zone_size;
>>>>>>>> +		u64 zoned;
>>>>>>>> +	};
>>>>>>>> +
>>>>>>>>      #ifdef CONFIG_BTRFS_FS_REF_VERIFY
>>>>>>>>      	spinlock_t ref_verify_lock;
>>>>>>>>      	struct rb_root block_tree;
>>>>>>>> @@ -3595,4 +3601,9 @@ static inline int btrfs_is_testing(struct btrfs_fs_info *fs_info)
>>>>>>>>      }
>>>>>>>>      #endif
>>>>>>>>      
>>>>>>>> +static inline bool btrfs_is_zoned(struct btrfs_fs_info *fs_info)
>>>>>>>> +{
>>>>>>>> +	return fs_info->zoned != 0;
>>>>>>>> +}
>>>>>>>> +
>>>>>>>>      #endif
>>>>>>>> diff --git a/fs/btrfs/dev-replace.c b/fs/btrfs/dev-replace.c
>>>>>>>> index 6f6d77224c2b..db87f1aa604b 100644
>>>>>>>> --- a/fs/btrfs/dev-replace.c
>>>>>>>> +++ b/fs/btrfs/dev-replace.c
>>>>>>>> @@ -238,6 +238,13 @@ static int btrfs_init_dev_replace_tgtdev(struct btrfs_fs_info *fs_info,
>>>>>>>>      		return PTR_ERR(bdev);
>>>>>>>>      	}
>>>>>>>>      
>>>>>>>> +	if (!btrfs_check_device_zone_type(fs_info, bdev)) {
>>>>>>>> +		btrfs_err(fs_info,
>>>>>>>> +			  "dev-replace: zoned type of target device mismatch with filesystem");
>>>>>>>> +		ret = -EINVAL;
>>>>>>>> +		goto error;
>>>>>>>> +	}
>>>>>>>> +
>>>>>>>>      	sync_blockdev(bdev);
>>>>>>>>      
>>>>>>>>      	list_for_each_entry(device, &fs_info->fs_devices->devices, dev_list) {
>>>>>>>
>>>>>>>      I am not sure if it is done in some other patch. But we still have to
>>>>>>>      check for
>>>>>>>
>>>>>>>      (model == BLK_ZONED_HA && incompat_zoned))
>>>>>>
>>>>>> Do you really mean BLK_ZONED_HA, ie. host-aware (HA)?
>>>>>> btrfs_check_device_zone_type checks for _HM.
>>>>>
>>>>>
>>>>> Still confusing to me. The below function, which is part of this
>>>>> patch, says we don't support BLK_ZONED_HM. So does it mean we
>>>>> allow BLK_ZONED_HA only?
>>>>>
>>>>> +static inline bool btrfs_check_device_zone_type(struct btrfs_fs_info
>>>>> *fs_info,
>>>>> +						struct block_device *bdev)
>>>>> +{
>>>>> +	u64 zone_size;
>>>>> +
>>>>> +	if (btrfs_is_zoned(fs_info)) {
>>>>> +		zone_size = (u64)bdev_zone_sectors(bdev) << SECTOR_SHIFT;
>>>>> +		/* Do not allow non-zoned device */
>>>>
>>>> This comment does not make sense. It should be:
>>>>
>>>> 		/* Only allow zoned devices with the same zone size */
>>>>
>>>>> +		return bdev_is_zoned(bdev) && fs_info->zone_size == zone_size;
>>>>> +	}
>>>>> +
>>>>> +	/* Do not allow Host Manged zoned device */
>>>>> +	return bdev_zoned_model(bdev) != BLK_ZONED_HM;
>>>>
>>>> The comment is also wrong. It should read:
>>>>
>>>> 	/* Allow only host managed zoned devices */
>>>>
>>>> This is because we decided to treat host aware devices in the same way as
>>>> regular block devices, since HA drives are backward compatible with regular
>>>> block devices.
>>>
>>>
>>> Yeah, I read about them, but I have questions like do an FS work on top
>>> of a BLK_ZONED_HA without modification?
>>
>> Yes. These drives are fully backward compatible and accept random writes
>> anywhere. Performance however is potentially a different story as the drive will
>> eventually need to do internal garbage collection of some sort, exactly like an
>> SSD, but definitely not at SSD speeds :)
>>
>>>    Are we ok to replace an HM device with a HA device? Or add a HA device
>>> to a btrfs on an HM device.
>>
>> We have a choice here: we can treat HA drives as regular devices or treat them
>> as HM devices. Anything in between does not make sense. I am fine either way,
>> the main reason being that there are no HA drive on the market today that I know
>> of (this model did not have a lot of success due to the potentially very
>> unpredictable performance depending on the use case).
>>
>> So the simplest thing to do is, in my opinion, to ignore their "zone"
>> characteristics and treat them as regular disks. But treating them as HM drives
>> is a simple to do too.
>>> Of note is that a host-aware drive will be reported by the block layer as
>> BLK_ZONED_HA only as long as the drive does not have any partition. If it does,
>> then the block layer will treat the drive as a regular disk.
> 
> IMO. For now, it is better to check for the BLK_ZONED_HA explicitly in a 
> non-zoned-btrfs. And check for BLK_ZONED_HM explicitly in a zoned-btrfs. 

Sure, we can. But since HA drives are backward compatible, not sure the HA check
for non-zoned make sense. As long as the zoned flag is not set, the drive can be
used like a regular disk. If the user really want to use it as a zoned drive,
then it can format with force selecting the zoned flag in btrfs super. Then the
HA drive will be used as a zoned disk, exactly like HM disks.

> This way, if there is another type of BLK_ZONED_xx in the future, we 
> have the opportunity to review to support it. As below [1]...

It is very unlikely that we will see any other zone model. ZNS adopted the HM
model in purpose, to avoid multiplying the possible models, making the ecosystem
effort a nightmare.

> 
> [1]
> bool btrfs_check_device_type()
> {
> 	if (bdev_is_zoned()) {
> 		if (btrfs_is_zoned())
> 			if (bdev_zoned_model == BLK_ZONED_HM)
> 			/* also check the zone_size. */
> 				return true;
> 		else
> 			if (bdev_zoned_model == BLK_ZONED_HA)
> 			/* a regular device and FS, no zone_size to check I think? */
> 				return true;
> 	} else {
> 		if (!btrfs_is_zoned())
> 			return true
> 	}
> 
> 	return false;
> }
> 
> Thanks.

Works for me. May be reverse the conditions to make things easier to read and
understand:

bool btrfs_check_device_type()
{
	if (btrfs_is_zoned()) {
		if (bdev_is_zoned()) {
			/* also check the zone_size. */
			return true;
		}

		/*
		 * Regular device: emulate zones with zone size equal
		 * to device extent size.
		 */
		return true;
	}

	if (bdev_zoned_model == BLK_ZONED_HM) {
		/* Zoned HM device require zoned btrfs */
		return false;
	}

	/* Regular device or zoned HA device used as a regular device */
	return true;
}


-- 
Damien Le Moal
Western Digital Research

  reply	other threads:[~2020-12-01  6:10 UTC|newest]

Thread overview: 125+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10 11:26 [PATCH v10 00/41] btrfs: zoned block device support Naohiro Aota
2020-11-10 11:26 ` [PATCH v10 01/41] block: add bio_add_zone_append_page Naohiro Aota
2020-11-10 17:20   ` Christoph Hellwig
2020-11-11  7:20     ` Johannes Thumshirn
2020-11-10 11:26 ` [PATCH v10 02/41] iomap: support REQ_OP_ZONE_APPEND Naohiro Aota
2020-11-10 17:25   ` Christoph Hellwig
2020-11-10 18:55   ` Darrick J. Wong
2020-11-10 19:01     ` Darrick J. Wong
2020-11-24 11:29     ` Christoph Hellwig
2020-11-30 18:11   ` Darrick J. Wong
2020-12-01 10:16     ` Johannes Thumshirn
2020-12-09  9:31   ` Christoph Hellwig
2020-12-09 10:08     ` Johannes Thumshirn
2020-12-09 10:10       ` hch
2020-12-09 10:16         ` Johannes Thumshirn
2020-12-09 13:38           ` Johannes Thumshirn
2020-12-11  7:26             ` Johannes Thumshirn
2020-12-11 21:24               ` Chaitanya Kulkarni
2020-12-12 10:22                 ` Johannes Thumshirn
2020-11-10 11:26 ` [PATCH v10 03/41] btrfs: introduce ZONED feature flag Naohiro Aota
2020-11-19 21:31   ` David Sterba
2020-11-10 11:26 ` [PATCH v10 04/41] btrfs: get zone information of zoned block devices Naohiro Aota
2020-11-12  6:57   ` Anand Jain
2020-11-12  7:35     ` Johannes Thumshirn
2020-11-12  7:44       ` Damien Le Moal
2020-11-12  9:44         ` Anand Jain
2020-11-13 21:34           ` David Sterba
2020-11-12  9:39     ` Johannes Thumshirn
2020-11-12 12:57     ` Naohiro Aota
2020-11-18 11:17       ` Anand Jain
2020-11-30 11:16         ` Anand Jain
2020-11-25 21:47   ` David Sterba
2020-11-25 22:07     ` David Sterba
2020-11-25 23:50     ` Damien Le Moal
2020-11-26 14:11       ` David Sterba
2020-11-25 22:16   ` David Sterba
2020-11-10 11:26 ` [PATCH v10 05/41] btrfs: check and enable ZONED mode Naohiro Aota
2020-11-18 11:29   ` Anand Jain
2020-11-27 18:44     ` David Sterba
2020-11-30 12:12       ` Anand Jain
2020-11-30 13:15         ` Damien Le Moal
2020-12-01  2:19           ` Anand Jain
2020-12-01  2:29             ` Damien Le Moal
2020-12-01  5:53               ` Anand Jain
2020-12-01  6:09                 ` Damien Le Moal [this message]
2020-12-01  7:12                   ` Anand Jain
2020-12-01 10:45               ` Graham Cobb
2020-12-01 11:03                 ` Damien Le Moal
2020-12-01 11:11                   ` hch
2020-12-01 11:27                     ` Damien Le Moal
2020-11-10 11:26 ` [PATCH v10 06/41] btrfs: introduce max_zone_append_size Naohiro Aota
2020-11-19  9:23   ` Anand Jain
2020-11-27 18:47     ` David Sterba
2020-11-10 11:26 ` [PATCH v10 07/41] btrfs: disallow space_cache in ZONED mode Naohiro Aota
2020-11-19 10:42   ` Anand Jain
2020-11-20  4:08     ` Anand Jain
2020-11-10 11:26 ` [PATCH v10 08/41] btrfs: disallow NODATACOW " Naohiro Aota
2020-11-20  4:17   ` Anand Jain
2020-11-23 17:21     ` David Sterba
2020-11-24  3:29       ` Anand Jain
2020-11-10 11:26 ` [PATCH v10 09/41] btrfs: disable fallocate " Naohiro Aota
2020-11-20  4:28   ` Anand Jain
2020-11-10 11:26 ` [PATCH v10 10/41] btrfs: disallow mixed-bg " Naohiro Aota
2020-11-20  4:32   ` Anand Jain
2020-11-10 11:26 ` [PATCH v10 11/41] btrfs: implement log-structured superblock for " Naohiro Aota
2020-11-11  1:34   ` kernel test robot
2020-11-11  2:43   ` kernel test robot
2020-11-23 17:46   ` David Sterba
2020-11-24  9:30     ` Johannes Thumshirn
2020-11-24  6:46   ` Anand Jain
2020-11-24  7:16     ` Hannes Reinecke
2020-11-10 11:26 ` [PATCH v10 12/41] btrfs: implement zoned chunk allocator Naohiro Aota
2020-11-24 11:36   ` Anand Jain
2020-11-25  1:57     ` Naohiro Aota
2020-11-25  7:17       ` Anand Jain
2020-11-25 11:48         ` Naohiro Aota
2020-11-25  9:59       ` Graham Cobb
2020-11-25 11:50         ` Naohiro Aota
2020-12-09  5:27   ` Anand Jain
2020-11-10 11:26 ` [PATCH v10 13/41] btrfs: verify device extent is aligned to zone Naohiro Aota
2020-11-27  6:27   ` Anand Jain
2020-11-10 11:26 ` [PATCH v10 14/41] btrfs: load zone's alloction offset Naohiro Aota
2020-12-08  9:54   ` Anand Jain
2020-11-10 11:26 ` [PATCH v10 15/41] btrfs: emulate write pointer for conventional zones Naohiro Aota
2020-11-10 11:26 ` [PATCH v10 16/41] btrfs: track unusable bytes for zones Naohiro Aota
2020-11-10 11:26 ` [PATCH v10 17/41] btrfs: do sequential extent allocation in ZONED mode Naohiro Aota
2020-11-10 11:26 ` [PATCH v10 18/41] btrfs: reset zones of unused block groups Naohiro Aota
2020-11-10 11:26 ` [PATCH v10 19/41] btrfs: redirty released extent buffers in ZONED mode Naohiro Aota
2020-11-10 11:26 ` [PATCH v10 20/41] btrfs: extract page adding function Naohiro Aota
2020-11-10 11:26 ` [PATCH v10 21/41] btrfs: use bio_add_zone_append_page for zoned btrfs Naohiro Aota
2020-11-10 11:26 ` [PATCH v10 22/41] btrfs: handle REQ_OP_ZONE_APPEND as writing Naohiro Aota
2020-11-10 11:26 ` [PATCH v10 23/41] btrfs: split ordered extent when bio is sent Naohiro Aota
2020-11-11  2:01   ` kernel test robot
2020-11-11  2:01     ` kernel test robot
2020-11-11  2:26   ` kernel test robot
2020-11-11  2:26     ` kernel test robot
2020-11-11  3:46   ` kernel test robot
2020-11-11  3:46     ` kernel test robot
2020-11-11  3:46   ` [RFC PATCH] btrfs: extract_ordered_extent() can be static kernel test robot
2020-11-11  3:46     ` kernel test robot
2020-11-11  4:12   ` [PATCH v10.1 23/41] btrfs: split ordered extent when bio is sent Naohiro Aota
2020-11-10 11:26 ` [PATCH v10 24/41] btrfs: extend btrfs_rmap_block for specifying a device Naohiro Aota
2020-11-10 11:26 ` [PATCH v10 25/41] btrfs: use ZONE_APPEND write for ZONED btrfs Naohiro Aota
2020-11-10 11:26 ` [PATCH v10 26/41] btrfs: enable zone append writing for direct IO Naohiro Aota
2020-11-10 11:26 ` [PATCH v10 27/41] btrfs: introduce dedicated data write path for ZONED mode Naohiro Aota
2020-11-10 11:26 ` [PATCH v10 28/41] btrfs: serialize meta IOs on " Naohiro Aota
2020-11-10 11:26 ` [PATCH v10 29/41] btrfs: wait existing extents before truncating Naohiro Aota
2020-11-10 11:26 ` [PATCH v10 30/41] btrfs: avoid async metadata checksum on ZONED mode Naohiro Aota
2020-11-10 11:26 ` [PATCH v10 31/41] btrfs: mark block groups to copy for device-replace Naohiro Aota
2020-11-11  3:13   ` kernel test robot
2020-11-11  3:16   ` kernel test robot
2020-11-10 11:26 ` [PATCH v10 32/41] btrfs: implement cloning for ZONED device-replace Naohiro Aota
2020-11-10 11:26 ` [PATCH v10 33/41] btrfs: implement copying " Naohiro Aota
2020-11-10 11:26 ` [PATCH v10 34/41] btrfs: support dev-replace in ZONED mode Naohiro Aota
2020-11-10 11:26 ` [PATCH v10 35/41] btrfs: enable relocation " Naohiro Aota
2020-11-10 11:26 ` [PATCH v10 36/41] btrfs: relocate block group to repair IO failure in ZONED Naohiro Aota
2020-11-10 11:26 ` [PATCH v10 37/41] btrfs: split alloc_log_tree() Naohiro Aota
2020-11-10 11:26 ` [PATCH v10 38/41] btrfs: extend zoned allocator to use dedicated tree-log block group Naohiro Aota
2020-11-11  4:58   ` [PATCH v10.1 " Naohiro Aota
2020-11-10 11:26 ` [PATCH v10 39/41] btrfs: serialize log transaction on ZONED mode Naohiro Aota
2020-11-10 11:26 ` [PATCH v10 40/41] btrfs: reorder log node allocation Naohiro Aota
2020-11-10 11:26 ` [PATCH v10 41/41] btrfs: enable to mount ZONED incompat flag Naohiro Aota
2020-11-10 14:00 ` [PATCH v10 00/41] btrfs: zoned block device support Anand Jain
2020-11-11  5:07   ` Naohiro Aota
2020-11-27 19:28 ` 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=CH2PR04MB652224DE2A682FADE28F443DE7F40@CH2PR04MB6522.namprd04.prod.outlook.com \
    --to=damien.lemoal@wdc.com \
    --cc=Johannes.Thumshirn@wdc.com \
    --cc=Naohiro.Aota@wdc.com \
    --cc=anand.jain@oracle.com \
    --cc=axboe@kernel.dk \
    --cc=darrick.wong@oracle.com \
    --cc=dsterba@suse.com \
    --cc=dsterba@suse.cz \
    --cc=hare@suse.com \
    --cc=hch@infradead.org \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.