From: Klaus Jensen <its@irrelevant.dk>
To: Dmitry Fomichev <dmitry.fomichev@wdc.com>
Cc: "Fam Zheng" <fam@euphon.net>, "Kevin Wolf" <kwolf@redhat.com>,
"Damien Le Moal" <damien.lemoal@wdc.com>,
qemu-block@nongnu.org, "Niklas Cassel" <niklas.cassel@wdc.com>,
"Klaus Jensen" <k.jensen@samsung.com>,
qemu-devel@nongnu.org, "Maxim Levitsky" <mlevitsk@redhat.com>,
"Alistair Francis" <alistair.francis@wdc.com>,
"Keith Busch" <kbusch@kernel.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Matias Bjorling" <matias.bjorling@wdc.com>
Subject: Re: [PATCH v3 10/15] hw/block/nvme: Support Zoned Namespace Command Set
Date: Fri, 18 Sep 2020 23:20:08 +0200 [thread overview]
Message-ID: <20200918212008.GA581752@apples.localdomain> (raw)
In-Reply-To: <20200913221436.22844-11-dmitry.fomichev@wdc.com>
[-- Attachment #1: Type: text/plain, Size: 3464 bytes --]
On Sep 14 07:14, 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>
> ---
> hw/block/nvme.c | 968 ++++++++++++++++++++++++++++++++++++++++++++++--
> 1 file changed, 939 insertions(+), 29 deletions(-)
>
> diff --git a/hw/block/nvme.c b/hw/block/nvme.c
> index c740cbcf1f..0bf7471815 100644
> --- a/hw/block/nvme.c
> +++ b/hw/block/nvme.c
> @@ -709,11 +965,77 @@ static uint16_t nvme_rw(NvmeCtrl *n, NvmeRequest *req)
> return status;
> }
>
> + if (n->params.zoned) {
> + zone_idx = nvme_zone_idx(n, slba);
> + assert(zone_idx < n->num_zones);
> + zone = &ns->zone_array[zone_idx];
> +
> + if (is_write) {
> + status = nvme_check_zone_write(zone, slba, nlb);
> + if (status != NVME_SUCCESS) {
> + trace_pci_nvme_err_zone_write_not_ok(slba, nlb, status);
> + return status | NVME_DNR;
> + }
> +
> + assert(nvme_wp_is_valid(zone));
> + if (append) {
> + if (unlikely(slba != zone->d.zslba)) {
> + trace_pci_nvme_err_append_not_at_start(slba, zone->d.zslba);
> + return NVME_ZONE_INVALID_WRITE | NVME_DNR;
> + }
> + if (data_size > (n->page_size << n->zasl)) {
> + trace_pci_nvme_err_append_too_large(slba, nlb, n->zasl);
> + return NVME_INVALID_FIELD | NVME_DNR;
> + }
> + slba = zone->d.wp;
Your append is broken.
Since you moved the write pointer update to post aio completion (which I
totally agree with), you are now assigning the same SLBA to all appends
that are in queue when nvme_process_sq is invoked.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-09-18 22:10 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-13 22:14 [PATCH v3 00/15] hw/block/nvme: Support Namespace Types and Zoned Namespace Command Set Dmitry Fomichev
2020-09-13 22:14 ` [PATCH v3 01/15] hw/block/nvme: Define 64 bit cqe.result Dmitry Fomichev
2020-09-15 7:37 ` Klaus Jensen
2020-09-15 18:56 ` Dmitry Fomichev
2020-09-15 19:55 ` Klaus Jensen
2020-09-15 20:44 ` Dmitry Fomichev
2020-09-15 20:48 ` Klaus Jensen
2020-09-18 21:10 ` Keith Busch
2020-09-21 21:39 ` Dmitry Fomichev
2020-09-13 22:14 ` [PATCH v3 02/15] hw/block/nvme: Report actual LBA data shift in LBAF Dmitry Fomichev
2020-09-15 7:34 ` Klaus Jensen
2020-09-15 18:57 ` Dmitry Fomichev
2020-09-13 22:14 ` [PATCH v3 03/15] hw/block/nvme: Add Commands Supported and Effects log Dmitry Fomichev
2020-09-13 22:14 ` [PATCH v3 04/15] hw/block/nvme: Introduce the Namespace Types definitions Dmitry Fomichev
2020-09-13 22:14 ` [PATCH v3 05/15] hw/block/nvme: Define trace events related to NS Types Dmitry Fomichev
2020-09-14 6:35 ` Philippe Mathieu-Daudé
2020-09-13 22:14 ` [PATCH v3 06/15] hw/block/nvme: Add support for Namespace Types Dmitry Fomichev
2020-09-18 21:29 ` Klaus Jensen
2020-09-18 22:22 ` Dmitry Fomichev
2020-09-13 22:14 ` [PATCH v3 07/15] hw/block/nvme: Add support for active/inactive namespaces Dmitry Fomichev
2020-09-13 22:14 ` [PATCH v3 08/15] hw/block/nvme: Make Zoned NS Command Set definitions Dmitry Fomichev
2020-09-13 22:14 ` [PATCH v3 09/15] hw/block/nvme: Define Zoned NS Command Set trace events Dmitry Fomichev
2020-09-13 22:14 ` [PATCH v3 10/15] hw/block/nvme: Support Zoned Namespace Command Set Dmitry Fomichev
2020-09-18 21:20 ` Klaus Jensen [this message]
2020-09-18 22:07 ` Dmitry Fomichev
2020-09-13 22:14 ` [PATCH v3 11/15] hw/block/nvme: Introduce max active and open zone limits Dmitry Fomichev
2020-09-13 22:14 ` [PATCH v3 12/15] hw/block/nvme: Support Zone Descriptor Extensions Dmitry Fomichev
2020-09-13 22:14 ` [PATCH v3 13/15] hw/block/nvme: Add injection of Offline/Read-Only zones Dmitry Fomichev
2020-09-13 22:14 ` [PATCH v3 14/15] hw/block/nvme: Use zone metadata file for persistence Dmitry Fomichev
2020-09-15 19:09 ` Klaus Jensen
2020-09-15 20:44 ` Dmitry Fomichev
2020-09-15 20:46 ` Klaus Jensen
2020-09-13 22:14 ` [PATCH v3 15/15] 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=20200918212008.GA581752@apples.localdomain \
--to=its@irrelevant.dk \
--cc=alistair.francis@wdc.com \
--cc=damien.lemoal@wdc.com \
--cc=dmitry.fomichev@wdc.com \
--cc=fam@euphon.net \
--cc=k.jensen@samsung.com \
--cc=kbusch@kernel.org \
--cc=kwolf@redhat.com \
--cc=matias.bjorling@wdc.com \
--cc=mlevitsk@redhat.com \
--cc=niklas.cassel@wdc.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).