From: "Matias Bjørling" <mb@lightnvm.io>
To: Alexey Dobriyan <adobriyan@gmail.com>, axboe@kernel.dk
Cc: linux-block@vger.kernel.org, damien.lemoal@wdc.com
Subject: Re: [PATCH v2] block: support arbitrary zone size
Date: Tue, 11 Feb 2020 00:28:17 +0100 [thread overview]
Message-ID: <afaa196d-ca85-3b6d-fa67-d25b24ff812e@lightnvm.io> (raw)
In-Reply-To: <20200210222045.GA1495@avx2>
On 10/02/2020 23.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>
> ---
Nack from here as well. The power of 2 is a strict requirement. All SMR
HDDs Zone Sizes are a power of two, and ZNS SSDs should be as well if
they want Linux eco-system support.
The ZNS specification is specifically written to accommodate this. It
has two type of zone sizes, the Zone Size (which is what should be a
power of two) and the Zone Capacity (that is the writable capacity of
the zone). For Linux support, your ZNS SSD implemention must have a zone
size that is power of two, and instead use the Zone Capacity field to be
the "Zone Size" that you have now. Then it works as expected, making
both the host and device happy. The host gets power of two, and device
can communicate the non-power of two writeable LBAs within the zone.
Best, Matias
next prev parent reply other threads:[~2020-02-10 23:28 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 [this message]
2020-02-11 17:16 ` Alexey Dobriyan
2020-02-11 9:16 ` Javier González
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=afaa196d-ca85-3b6d-fa67-d25b24ff812e@lightnvm.io \
--to=mb@lightnvm.io \
--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).