From: "Javier González" <javier@javigon.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: axboe@kernel.dk, linux-block@vger.kernel.org, damien.lemoal@wdc.com
Subject: Re: [PATCH v2] block: support arbitrary zone size
Date: Tue, 11 Feb 2020 10:16:37 +0100 [thread overview]
Message-ID: <20200211091637.nkawa73iwgznqgcm@mpHalley.local> (raw)
In-Reply-To: <20200210222045.GA1495@avx2>
On 11.02.2020 01:20, Alexey Dobriyan wrote:
>SK hynix is going to ship ZNS device with zone size not being power of 2.
>
>Signed-off-by: Alexey Dobriyan (SK hynix) <adobriyan@gmail.com>
>---
>
> v2: fixup one ">>ilog2"/div conversion :-/
>
> block/blk-settings.c | 4 +---
> block/blk-zoned.c | 10 +++++-----
> drivers/block/null_blk_main.c | 11 ++++++-----
> drivers/block/null_blk_zoned.c | 10 ++--------
> 4 files changed, 14 insertions(+), 21 deletions(-)
>
>--- a/block/blk-settings.c
>+++ b/block/blk-settings.c
>@@ -206,15 +206,13 @@ EXPORT_SYMBOL(blk_queue_max_hw_sectors);
> *
> * Description:
> * If a driver doesn't want IOs to cross a given chunk size, it can set
>- * this limit and prevent merging across chunks. Note that the chunk size
>- * must currently be a power-of-2 in sectors. Also note that the block
>+ * this limit and prevent merging across chunks. Note that the block
> * layer must accept a page worth of data at any offset. So if the
> * crossing of chunks is a hard limitation in the driver, it must still be
> * prepared to split single page bios.
> **/
> void blk_queue_chunk_sectors(struct request_queue *q, unsigned int chunk_sectors)
> {
>- BUG_ON(!is_power_of_2(chunk_sectors));
> q->limits.chunk_sectors = chunk_sectors;
> }
> EXPORT_SYMBOL(blk_queue_chunk_sectors);
>--- a/block/blk-zoned.c
>+++ b/block/blk-zoned.c
>@@ -83,7 +83,7 @@ unsigned int blkdev_nr_zones(struct gendisk *disk)
>
> if (!blk_queue_is_zoned(disk->queue))
> return 0;
>- return (get_capacity(disk) + zone_sectors - 1) >> ilog2(zone_sectors);
>+ return div64_u64(get_capacity(disk) + zone_sectors - 1, zone_sectors);
> }
> EXPORT_SYMBOL_GPL(blkdev_nr_zones);
>
>@@ -363,14 +363,14 @@ static int blk_revalidate_zone_cb(struct blk_zone *zone, unsigned int idx,
> * smaller last zone.
> */
> if (zone->start == 0) {
>- if (zone->len == 0 || !is_power_of_2(zone->len)) {
>- pr_warn("%s: Invalid zoned device with non power of two zone size (%llu)\n",
>- disk->disk_name, zone->len);
>+ if (zone->len == 0) {
>+ pr_warn("%s: Invalid zoned device with length 0\n",
>+ disk->disk_name);
> return -ENODEV;
> }
>
> args->zone_sectors = zone->len;
>- args->nr_zones = (capacity + zone->len - 1) >> ilog2(zone->len);
>+ args->nr_zones = div64_u64(capacity + zone->len - 1, zone->len);
> } else if (zone->start + args->zone_sectors < capacity) {
> if (zone->len != args->zone_sectors) {
> pr_warn("%s: Invalid zoned device with non constant zone size\n",
>--- a/drivers/block/null_blk_main.c
>+++ b/drivers/block/null_blk_main.c
>@@ -187,7 +187,7 @@ MODULE_PARM_DESC(zoned, "Make device as a host-managed zoned block device. Defau
>
> static unsigned long g_zone_size = 256;
> module_param_named(zone_size, g_zone_size, ulong, S_IRUGO);
>-MODULE_PARM_DESC(zone_size, "Zone size in MB when block device is zoned. Must be power-of-two: Default: 256");
>+MODULE_PARM_DESC(zone_size, "Zone size in MB when block device is zoned. Default: 256");
>
> static unsigned int g_zone_nr_conv;
> module_param_named(zone_nr_conv, g_zone_nr_conv, uint, 0444);
>@@ -1641,10 +1641,11 @@ static int null_validate_conf(struct nullb_device *dev)
> if (dev->queue_mode == NULL_Q_BIO)
> dev->mbps = 0;
>
>- if (dev->zoned &&
>- (!dev->zone_size || !is_power_of_2(dev->zone_size))) {
>- pr_err("zone_size must be power-of-two\n");
>- return -EINVAL;
>+ if (dev->zoned) {
>+ if (dev->zone_size == 0) {
>+ pr_err("zone_size must be positive\n");
>+ return -EINVAL;
>+ }
> }
>
> return 0;
>--- a/drivers/block/null_blk_zoned.c
>+++ b/drivers/block/null_blk_zoned.c
>@@ -7,7 +7,7 @@
>
> static inline unsigned int null_zone_no(struct nullb_device *dev, sector_t sect)
> {
>- return sect >> ilog2(dev->zone_size_sects);
>+ return div64_u64(sect, dev->zone_size_sects);
> }
>
> int null_zone_init(struct nullb_device *dev)
>@@ -16,14 +16,8 @@ int null_zone_init(struct nullb_device *dev)
> sector_t sector = 0;
> unsigned int i;
>
>- if (!is_power_of_2(dev->zone_size)) {
>- pr_err("zone_size must be power-of-two\n");
>- return -EINVAL;
>- }
>-
> dev->zone_size_sects = dev->zone_size << ZONE_SIZE_SHIFT;
>- dev->nr_zones = dev_size >>
>- (SECTOR_SHIFT + ilog2(dev->zone_size_sects));
>+ dev->nr_zones = div64_u64(dev_size, dev->zone_size_sects * SECTOR_SIZE);
> dev->zones = kvmalloc_array(dev->nr_zones, sizeof(struct blk_zone),
> GFP_KERNEL | __GFP_ZERO);
> if (!dev->zones)
Same response from here. You will need to add some changes to support
arbitrary zone capacities, but the zone size needs to be a power-of-2 to
plug into the zoned framework.
Javier
next prev parent reply other threads:[~2020-02-11 9:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 22:08 [PATCH] block: support arbitrary zone size Alexey Dobriyan
2020-02-10 22:20 ` [PATCH v2] " Alexey Dobriyan
2020-02-10 22:57 ` Damien Le Moal
2020-02-10 23:06 ` Martin K. Petersen
2020-02-10 23:28 ` Matias Bjørling
2020-02-11 17:16 ` Alexey Dobriyan
2020-02-11 9:16 ` Javier González [this message]
2020-02-12 20:00 ` Christoph Hellwig
2020-02-10 22:23 ` [PATCH] " Bart Van Assche
2020-02-10 22:33 ` Keith Busch
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=20200211091637.nkawa73iwgznqgcm@mpHalley.local \
--to=javier@javigon.com \
--cc=adobriyan@gmail.com \
--cc=axboe@kernel.dk \
--cc=damien.lemoal@wdc.com \
--cc=linux-block@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).