From: Klaus Jensen <its@irrelevant.dk>
To: clay.mayers@kioxia.com
Cc: qemu-devel@nongnu.org, "Keith Busch" <kbusch@kernel.org>,
"Fam Zheng" <fam@euphon.net>,
"Phlippe Mathieu-Daudé" <f4bug@amsat.org>,
"Dmitry Fomichev" <dmitry.fomichev@wdc.com>
Subject: Re: [PATCH V2 0/4] hw/block/nvme: Implement ZNS finish-zone ZDC AEN
Date: Wed, 9 Nov 2022 09:40:15 +0100 [thread overview]
Message-ID: <Y2tnb2AIOX4nyykC@cormorant.local> (raw)
In-Reply-To: <20221021231038.1042659-1-clay.mayers@kioxia.com>
[-- Attachment #1: Type: text/plain, Size: 2231 bytes --]
On Oct 21 16:10, clay.mayers@kioxia.com wrote:
> From: Clay Mayers <clay.mayers@kioxia.com>
>
> ZNS controllers have the option to limit the time a zone can remain in
> the active state. It begins with a background process in the controller
> setting the finish-zone-recommended FZR attribute for a zone. As part of
> setting this attribute, the zone's id is added to the namespace's
> zone-descriptor-changed (ZDC) log page. If enabled, items added to the
> ZDC log page generate a ZDC "asynchronous event notification" AEN. Optionally,
> the control can induce a "zone excursion" forcing the zone into the finished
> state that also generates a ZDC event.
>
> Zone enabled applications need to properly handle ZDC events. In a real device,
> the timeout is many hours making testing an application difficult.
> Implemented is the generation of FZR ZDC events to speed up O/S and application
> testing.
>
> Added to the zoned NVMe command set is an optional, per-namespace timer
> (zoned.finish_time) to set the FZR attr for long-lived active zones; A per
> namespace ZDC log page; AEN results to including CQE.DW1 (the NSID of the ZDC
> AEN) and generating a ZDC AEN if it's been enabled. Zone excursions are not
> modeled.
>
> See section 5.5 of the NVMe Zoned Namespace Command Set Specification v1.1
> for more details.
>
> Changes since v1
> - Fixed offset length checking in zdc log page
> - Moved zdc_event_queued to the patch 4
> - Unwatched zdc events in nvme_exit()
>
> Clay Mayers (4):
> hw/block/nvme: add ZONE_FINISH_RECOMMENDED functionality
> hw/block/nvme: add zone descriptor changed log page
> hw/block/nvme: supply dw1 for aen result
> hw/block/nvme: add zone descriptor changed AEN
>
> docs/system/devices/nvme.rst | 5 +
> hw/nvme/ctrl.c | 174 +++++++++++++++++++++++++++++++++--
> hw/nvme/ns.c | 15 +++
> hw/nvme/nvme.h | 37 +++++++-
> hw/nvme/trace-events | 3 +-
> include/block/nvme.h | 14 ++-
> 6 files changed, 233 insertions(+), 15 deletions(-)
>
> --
> 2.27.0
>
Nice work Clay!
Series looks good to me,
Reviewed-by: Klaus Jensen <k.jensen@samsung.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-11-09 8:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 23:10 [PATCH V2 0/4] hw/block/nvme: Implement ZNS finish-zone ZDC AEN clay.mayers
2022-10-21 23:10 ` [PATCH V2 1/4] hw/block/nvme: add ZONE_FINISH_RECOMMENDED functionality clay.mayers
2022-10-21 23:10 ` [PATCH V2 2/4] hw/block/nvme: add zone descriptor changed log page clay.mayers
2022-10-21 23:10 ` [PATCH V2 3/4] hw/block/nvme: supply dw1 for aen result clay.mayers
2022-10-21 23:10 ` [PATCH V2 4/4] hw/block/nvme: add zone descriptor changed AEN clay.mayers
2022-10-24 15:22 ` [PATCH V2 0/4] hw/block/nvme: Implement ZNS finish-zone ZDC AEN Clay Mayers
2022-11-09 8:40 ` Klaus Jensen [this message]
2022-11-23 1:03 ` Clay Mayers
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=Y2tnb2AIOX4nyykC@cormorant.local \
--to=its@irrelevant.dk \
--cc=clay.mayers@kioxia.com \
--cc=dmitry.fomichev@wdc.com \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--cc=kbusch@kernel.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).