From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: "clay.mayers@kioxia.com" <clay.mayers@kioxia.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@fb.com>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>
Subject: Re: [PATCH V2 0/2] nvme: Support user mode processing of ZNS Zone Changed AEN
Date: Tue, 4 Oct 2022 01:48:33 +0000 [thread overview]
Message-ID: <1cef55e7-26a3-abac-315c-5f7f56f4771e@nvidia.com> (raw)
In-Reply-To: <20220929223955.3275715-1-clay.mayers@kioxia.com>
On 9/29/22 15:39, clay.mayers@kioxia.com wrote:
> From: Clay Mayers <clay.mayers@kioxia.com>
>
> This adds support for the ZNS Zone-Descriptor-Changes AEN, which is of
> type notify and uses CQE.DW1 to convey the NSID of the log page to read.
>
> Patch 1 adds non-zero NVME_AEN_DATA with the value of CQE.DW1 to all
> NVME_AEN uevents.
>
> Patch 2 generates a uevent for all unhandled AEN notify results instead
> of issuing a dev warning.
>
> This support is planned to be used by both zone based applications and
> another unreleased device with an alternate command set.
>
>
Please write a testcase in the blktest to this will get tested every
release.
-ck
next prev parent reply other threads:[~2022-10-04 1:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 22:39 [PATCH V2 0/2] nvme: Support user mode processing of ZNS Zone Changed AEN clay.mayers
2022-09-29 22:39 ` [PATCH V2 1/2] nvme: Include AEN CQE.DW1 in NVME_AEN uevents clay.mayers
2022-10-17 13:23 ` Christoph Hellwig
2022-10-18 20:12 ` Clay Mayers
2022-10-25 15:38 ` Christoph Hellwig
2022-10-25 15:59 ` Sagi Grimberg
2022-10-29 0:47 ` Clay Mayers
2022-09-29 22:39 ` [PATCH V2 2/2] nvme: All AENs of type notify generate an NVME_AEN uevent clay.mayers
2022-10-04 1:48 ` Chaitanya Kulkarni [this message]
2022-10-04 19:09 ` [PATCH V2 0/2] nvme: Support user mode processing of ZNS Zone Changed AEN Clay Mayers
2022-10-07 4:59 ` Chaitanya Kulkarni
2022-10-06 11:33 ` Sagi Grimberg
2022-10-06 20:16 ` 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=1cef55e7-26a3-abac-315c-5f7f56f4771e@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=axboe@fb.com \
--cc=clay.mayers@kioxia.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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).