From: "Belanger, Martin" <Martin.Belanger@dell.com>
To: Christoph Hellwig <hch@lst.de>,
Martin Belanger <nitram_67@hotmail.com>,
"Rao, Vinay" <Vinay.Rao@dell.com>,
"Hayes, Stuart" <Stuart.Hayes@dell.com>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"kbusch@kernel.org" <kbusch@kernel.org>,
"axboe@fb.com" <axboe@fb.com>,
"sagi@grimberg.me" <sagi@grimberg.me>
Subject: Re: [PATCH 1/1] nvme-fabrics: Generate uevent on namespace AENs
Date: Thu, 29 Apr 2021 16:58:39 +0000 [thread overview]
Message-ID: <SJ0PR19MB454499BF2899EF772B1EA11CF25F9@SJ0PR19MB4544.namprd19.prod.outlook.com> (raw)
In-Reply-To: <20210429063056.GA2482@lst.de>
++Vinay Rao, Stuart Hayes.
________________________________________
From: Christoph Hellwig <hch@lst.de>
Sent: Thursday, April 29, 2021 02:30
To: Martin Belanger
Cc: linux-nvme@lists.infradead.org; kbusch@kernel.org; axboe@fb.com; hch@lst.de; sagi@grimberg.me; Belanger, Martin; Belanger, Martin
Subject: Re: [PATCH 1/1] nvme-fabrics: Generate uevent on namespace AENs
[EXTERNAL EMAIL]
On Wed, Apr 28, 2021 at 04:18:25PM -0400, Martin Belanger wrote:
> From: Martin Belanger <martin.belanger@dell.com>
>
> Generate uevent on NVMe Async Event Notifications for NS_CHANGED and ANA. Today
> the uevent handler is not capturing on NVME_AER_NOTICE_NS_CHANGED
> (Namespace Changed) and NVME_AER_NOTICE_ANA (Asymmetric Namespace Access).
So the problem with these events is that they are only really useful
to then issue the Get Log Page command for the corresponding log page.
But reading the log page will clear the contents of the log page. That
is if userspace races to do this first it will completely mess up the
funtionality in the kernel.
This is a bit of an unfortunately design issue in the NVMe protocol.
Maybe you can explain you use case in a little more detail so that we
can figure out what we can do instead.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-04-29 16:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 20:18 [PATCH 1/1] nvme-fabrics: Generate uevent on namespace AENs Martin Belanger
2021-04-29 1:18 ` Chaitanya Kulkarni
2021-04-29 1:24 ` Chaitanya Kulkarni
2021-04-29 6:30 ` Christoph Hellwig
2021-04-29 16:58 ` Belanger, Martin [this message]
2021-04-29 18:22 ` Chaitanya Kulkarni
2021-04-30 5:14 ` Rao, Vinay
2021-04-30 16:21 ` Keith Busch
2021-05-03 6:52 ` Christoph Hellwig
2021-05-03 7:20 ` Rao, Vinay
2021-05-03 23:20 ` Chaitanya Kulkarni
2021-05-03 23:21 ` Chaitanya Kulkarni
2021-05-04 8:32 ` Rao, Vinay
2021-05-11 8:53 ` Rao, Vinay
2021-06-16 10:38 ` Rao, Vinay
2021-06-24 9:10 ` Hannes Reinecke
2021-06-24 9:17 ` Hannes Reinecke
2021-06-24 10:49 ` Hannes Reinecke
2021-06-30 14:00 ` Rao, Vinay
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=SJ0PR19MB454499BF2899EF772B1EA11CF25F9@SJ0PR19MB4544.namprd19.prod.outlook.com \
--to=martin.belanger@dell.com \
--cc=Stuart.Hayes@dell.com \
--cc=Vinay.Rao@dell.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=nitram_67@hotmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.