From: Dmitry Fomichev <Dmitry.Fomichev@wdc.com>
To: "its@irrelevant.dk" <its@irrelevant.dk>
Cc: "fam@euphon.net" <fam@euphon.net>,
Niklas Cassel <Niklas.Cassel@wdc.com>,
Damien Le Moal <Damien.LeMoal@wdc.com>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>,
"k.jensen@samsung.com" <k.jensen@samsung.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"mlevitsk@redhat.com" <mlevitsk@redhat.com>,
Alistair Francis <Alistair.Francis@wdc.com>,
"kbusch@kernel.org" <kbusch@kernel.org>,
"kwolf@redhat.com" <kwolf@redhat.com>,
"philmd@redhat.com" <philmd@redhat.com>,
Matias Bjorling <Matias.Bjorling@wdc.com>
Subject: Re: [PATCH v5 09/14] hw/block/nvme: Support Zoned Namespace Command Set
Date: Sun, 4 Oct 2020 23:48:04 +0000 [thread overview]
Message-ID: <2f864a8f274f7e4838d4930efc4ee2b8b05a1c2f.camel@wdc.com> (raw)
In-Reply-To: <20200930055935.GB436843@apples.localdomain>
On Wed, 2020-09-30 at 07:59 +0200, Klaus Jensen wrote:
> On Sep 28 11:35, Dmitry Fomichev wrote:
> > The emulation code has been changed to advertise NVM Command Set when
> > "zoned" device property is not set (default) and Zoned Namespace
> > Command Set otherwise.
> >
> > Handlers for three new NVMe commands introduced in Zoned Namespace
> > Command Set specification are added, namely for Zone Management
> > Receive, Zone Management Send and Zone Append.
> >
> > Device initialization code has been extended to create a proper
> > configuration for zoned operation using device properties.
> >
> > Read/Write command handler is modified to only allow writes at the
> > write pointer if the namespace is zoned. For Zone Append command,
> > writes implicitly happen at the write pointer and the starting write
> > pointer value is returned as the result of the command. Write Zeroes
> > handler is modified to add zoned checks that are identical to those
> > done as a part of Write flow.
> >
> > The code to support for Zone Descriptor Extensions is not included in
> > this commit and ZDES 0 is always reported. A later commit in this
> > series will add ZDE support.
> >
> > This commit doesn't yet include checks for active and open zone
> > limits. It is assumed that there are no limits on either active or
> > open zones.
> >
> > Signed-off-by: Niklas Cassel <niklas.cassel@wdc.com>
> > Signed-off-by: Hans Holmberg <hans.holmberg@wdc.com>
> > Signed-off-by: Ajay Joshi <ajay.joshi@wdc.com>
> > Signed-off-by: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
> > Signed-off-by: Matias Bjorling <matias.bjorling@wdc.com>
> > Signed-off-by: Aravind Ramesh <aravind.ramesh@wdc.com>
> > Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
> > Signed-off-by: Adam Manzanares <adam.manzanares@wdc.com>
> > Signed-off-by: Dmitry Fomichev <dmitry.fomichev@wdc.com>
> > ---
> > block/nvme.c | 2 +-
> > hw/block/nvme-ns.c | 185 ++++++++-
> > hw/block/nvme-ns.h | 6 +-
> > hw/block/nvme.c | 872 +++++++++++++++++++++++++++++++++++++++++--
> > include/block/nvme.h | 6 +-
> > 5 files changed, 1033 insertions(+), 38 deletions(-)
> >
> > diff --git a/block/nvme.c b/block/nvme.c
> > index 05485fdd11..7a513c9a17 100644
> > --- a/block/nvme.c
> > +++ b/block/nvme.c
> > +static int nvme_calc_zone_geometry(NvmeNamespace *ns, Error **errp)
> > +{
> > + uint64_t zone_size, zone_cap;
> > + uint32_t nz, lbasz = ns->blkconf.logical_block_size;
> > +
> > + if (ns->params.zone_size_mb) {
> > + zone_size = ns->params.zone_size_mb;
> > + } else {
> > + zone_size = NVME_DEFAULT_ZONE_SIZE;
> > + }
> > + if (ns->params.zone_capacity_mb) {
> > + zone_cap = ns->params.zone_capacity_mb;
> > + } else {
> > + zone_cap = zone_size;
> > + }
>
> I think a check that zone_capacity_mb is less than or equal to
> zone_size_mb is missing earlier?
The check is right below, but I now think it is better to
compare byte sizes rather than numbers of LBAs. There are also
checks missing for zone_size >= lbasz and zone_cap >= lbasz that
I am adding.
>
> > +static int nvme_zoned_init_ns(NvmeCtrl *n, NvmeNamespace *ns, int lba_index,
> > + Error **errp)
> > +{
> > + NvmeIdNsZoned *id_ns_z;
> > +
> > + if (n->params.fill_pattern == 0) {
> > + ns->id_ns.dlfeat |= 0x01;
> > + } else if (n->params.fill_pattern == 0xff) {
> > + ns->id_ns.dlfeat |= 0x02;
> > + }
> > +
> > + if (nvme_calc_zone_geometry(ns, errp) != 0) {
> > + return -1;
> > + }
> > +
> > + nvme_init_zone_meta(ns);
> > +
> > + id_ns_z = g_malloc0(sizeof(NvmeIdNsZoned));
> > +
> > + /* MAR/MOR are zeroes-based, 0xffffffff means no limit */
> > + id_ns_z->mar = 0xffffffff;
> > + id_ns_z->mor = 0xffffffff;
> > + id_ns_z->zoc = 0;
> > + id_ns_z->ozcs = ns->params.cross_zone_read ? 0x01 : 0x00;
> > +
> > + id_ns_z->lbafe[lba_index].zsze = cpu_to_le64(ns->zone_size);
> > + id_ns_z->lbafe[lba_index].zdes = 0; /* FIXME make helper */
> > +
> > + ns->csi = NVME_CSI_ZONED;
> > + ns->id_ns.ncap = cpu_to_le64(ns->zone_capacity * ns->num_zones);
> > + ns->id_ns.nuse = ns->id_ns.ncap;
> > + ns->id_ns.nsze = ns->id_ns.ncap;
> > +
>
> NSZE should be in terms of ZSZE. We *can* report NCAP < NSZE if zcap !=
> zsze, but that requires bit 1 set in NSFEAT and proper reporting of
> NUSE.
Ok, will correct. I think it used to be this way, but got messed up
during multiple transformations of this code.
>
> > @@ -133,6 +304,14 @@ static void nvme_ns_realize(DeviceState *dev, Error **errp)
> > static Property nvme_ns_props[] = {
> > DEFINE_BLOCK_PROPERTIES(NvmeNamespace, blkconf),
> > DEFINE_PROP_UINT32("nsid", NvmeNamespace, params.nsid, 0),
> > +
> > + DEFINE_PROP_BOOL("zoned", NvmeNamespace, params.zoned, false),
> > + DEFINE_PROP_UINT64("zone_size", NvmeNamespace, params.zone_size_mb,
> > + NVME_DEFAULT_ZONE_SIZE),
> > + DEFINE_PROP_UINT64("zone_capacity", NvmeNamespace,
> > + params.zone_capacity_mb, 0),
>
> There is a nice DEFINE_PROP_SIZE that handles sizes in a nice way (i.e.
> 1G, 1M).
It should be nice to use these types, will add them. _SIZE32 sounds like
a good candidate to use for ZASL.
Thank you for your valuable feedback!
>
next prev parent reply other threads:[~2020-10-04 23:49 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 2:35 [PATCH v5 00/14] hw/block/nvme: Support Namespace Types and Zoned Namespace Command Set Dmitry Fomichev
2020-09-28 2:35 ` [PATCH v5 01/14] hw/block/nvme: Report actual LBA data shift in LBAF Dmitry Fomichev
2020-09-28 8:51 ` Klaus Jensen
2020-09-28 2:35 ` [PATCH v5 02/14] hw/block/nvme: Add Commands Supported and Effects log Dmitry Fomichev
2020-09-28 2:35 ` [PATCH v5 03/14] hw/block/nvme: Introduce the Namespace Types definitions Dmitry Fomichev
2020-09-30 8:08 ` Klaus Jensen
2020-09-30 15:21 ` Keith Busch
2020-09-28 2:35 ` [PATCH v5 04/14] hw/block/nvme: Define trace events related to NS Types Dmitry Fomichev
2020-09-28 2:35 ` [PATCH v5 05/14] hw/block/nvme: Add support for Namespace Types Dmitry Fomichev
2020-09-30 8:15 ` Klaus Jensen
2020-09-30 12:47 ` Niklas Cassel
2020-10-01 11:22 ` Niklas Cassel
2020-10-01 15:29 ` Keith Busch
2020-10-01 15:50 ` Niklas Cassel
2020-10-01 15:59 ` Keith Busch
2020-10-01 16:23 ` Niklas Cassel
2020-10-01 17:08 ` Keith Busch
2020-10-01 22:15 ` Klaus Jensen
2020-10-01 22:30 ` Dmitry Fomichev
2020-09-28 2:35 ` [PATCH v5 06/14] hw/block/nvme: Add support for active/inactive namespaces Dmitry Fomichev
2020-09-30 13:50 ` Niklas Cassel
2020-10-04 23:54 ` Dmitry Fomichev
2020-10-05 11:26 ` Niklas Cassel
2020-09-28 2:35 ` [PATCH v5 07/14] hw/block/nvme: Make Zoned NS Command Set definitions Dmitry Fomichev
2020-09-28 2:35 ` [PATCH v5 08/14] hw/block/nvme: Define Zoned NS Command Set trace events Dmitry Fomichev
2020-09-28 2:35 ` [PATCH v5 09/14] hw/block/nvme: Support Zoned Namespace Command Set Dmitry Fomichev
2020-09-28 6:44 ` Klaus Jensen
2020-09-28 10:42 ` Klaus Jensen
2020-09-30 5:20 ` Klaus Jensen
2020-10-05 0:53 ` Dmitry Fomichev
2020-09-30 5:59 ` Klaus Jensen
2020-10-04 23:48 ` Dmitry Fomichev [this message]
2020-09-30 14:50 ` Niklas Cassel
2020-09-30 18:23 ` Klaus Jensen
2020-10-04 23:57 ` Dmitry Fomichev
2020-10-05 11:41 ` Niklas Cassel
2020-10-05 23:08 ` Dmitry Fomichev
2020-09-30 15:12 ` Niklas Cassel
2020-09-28 2:35 ` [PATCH v5 10/14] hw/block/nvme: Introduce max active and open zone limits Dmitry Fomichev
2020-09-28 2:35 ` [PATCH v5 11/14] hw/block/nvme: Support Zone Descriptor Extensions Dmitry Fomichev
2020-09-28 2:35 ` [PATCH v5 12/14] hw/block/nvme: Add injection of Offline/Read-Only zones Dmitry Fomichev
2020-09-28 2:35 ` [PATCH v5 13/14] hw/block/nvme: Use zone metadata file for persistence Dmitry Fomichev
2020-09-28 7:51 ` Klaus Jensen
2020-09-29 15:43 ` Dmitry Fomichev
2020-09-29 16:46 ` Klaus Jensen
2020-09-28 2:35 ` [PATCH v5 14/14] hw/block/nvme: Document zoned parameters in usage text Dmitry Fomichev
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=2f864a8f274f7e4838d4930efc4ee2b8b05a1c2f.camel@wdc.com \
--to=dmitry.fomichev@wdc.com \
--cc=Alistair.Francis@wdc.com \
--cc=Damien.LeMoal@wdc.com \
--cc=Matias.Bjorling@wdc.com \
--cc=Niklas.Cassel@wdc.com \
--cc=fam@euphon.net \
--cc=its@irrelevant.dk \
--cc=k.jensen@samsung.com \
--cc=kbusch@kernel.org \
--cc=kwolf@redhat.com \
--cc=mlevitsk@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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).