From: Daniel Wagner <dwagner@suse.de>
To: Nilay Shroff <nilay@linux.ibm.com>
Cc: Chaitanya Kulkarni <chaitanyak@nvidia.com>,
"shinichiro.kawasaki@wdc.com" <shinichiro.kawasaki@wdc.com>,
"hch@lst.de" <hch@lst.de>,
"kbusch@kernel.org" <kbusch@kernel.org>,
"sagi@grimberg.me" <sagi@grimberg.me>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"linux-nvme@lists.infradead.org"
<linux-nvme@lists.infradead.org>,
"gjoyce@linux.ibm.com" <gjoyce@linux.ibm.com>
Subject: Re: [PATCHv2 blktests 2/2] nvme: add test for writing to file-ns just after disabling it
Date: Thu, 5 Dec 2024 12:20:40 +0100 [thread overview]
Message-ID: <7775ee47-980f-4f2f-8642-cfbeb984df30@flourine.local> (raw)
In-Reply-To: <fb1058c3-ca47-4a54-8c1b-7eb9fa449fa0@linux.ibm.com>
On Thu, Dec 05, 2024 at 04:36:26PM +0530, Nilay Shroff wrote:
> Sure, you may refer "5.27.1.8 Asynchronous Event Configuration (Feature Identifier 0Bh)"
> in NVMe base spec 2.0. And then refer Figure 236, Namespace Attribute
> Notices:
Attached Namespace Attribute Notices (NAN): This bit determines
whether an asynchronous event notification is sent to the host for an
Attached Namespace Attribute Changed asynchronous event (refer to
Figure 151). If this bit is set to ‘1’, then the Attached Namespace
Attribute Changed asynchronous event is sent to the host when this
condition occurs. If this bit is cleared to ‘0’, then the controller
shall not send the Attached Namespace Attribute Changed asynchronous
event to the host.
I agree, doesn't say that the controller always has to send a NAN AEN.
next prev parent reply other threads:[~2024-12-05 11:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 11:47 [PATCHv2 blktests 0/2] add nvme test for creating sleep while atomic kernel BUG Nilay Shroff
2024-12-04 11:47 ` [PATCHv2 blktests 1/2] nvme/052: move nvmf_wait_for_ns() to common/nvme Nilay Shroff
2024-12-04 11:47 ` [PATCHv2 blktests 2/2] nvme: add test for writing to file-ns just after disabling it Nilay Shroff
2024-12-05 7:32 ` Chaitanya Kulkarni
2024-12-05 9:40 ` Nilay Shroff
2024-12-05 10:47 ` Daniel Wagner
2024-12-05 11:06 ` Nilay Shroff
2024-12-05 11:20 ` Daniel Wagner [this message]
2024-12-06 1:49 ` Shinichiro Kawasaki
2024-12-06 1:53 ` Shinichiro Kawasaki
2024-12-06 10:54 ` Nilay Shroff
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=7775ee47-980f-4f2f-8642-cfbeb984df30@flourine.local \
--to=dwagner@suse.de \
--cc=axboe@kernel.dk \
--cc=chaitanyak@nvidia.com \
--cc=gjoyce@linux.ibm.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=nilay@linux.ibm.com \
--cc=sagi@grimberg.me \
--cc=shinichiro.kawasaki@wdc.com \
/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