From: "hch@lst.de" <hch@lst.de>
To: "Knight, Frederick" <Frederick.Knight@netapp.com>
Cc: "George, Martin" <Martin.George@netapp.com>,
Hannes Reinecke <hare@suse.com>,
"sagi@grimberg.me" <sagi@grimberg.me>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
Keith Busch <kbusch@kernel.org>, "hch@lst.de" <hch@lst.de>,
"Meneghini, John" <John.Meneghini@netapp.com>
Subject: Re: [PATCH] nvme-core: update NS Attr Changed AEN handling for ANA group
Date: Wed, 9 Dec 2020 08:28:06 +0100 [thread overview]
Message-ID: <20201209072806.GA10037@lst.de> (raw)
In-Reply-To: <DM5PR0601MB362434919691D589BCCF637BF1CC0@DM5PR0601MB3624.namprd06.prod.outlook.com>
Fred, stop this bullshit now! I'm sick and tired of you misrepresenting my
opinion again and again despite me correcting you. This is not a basis for
productive work.
The only thing I requested is what is said in the document:
"A controller shall not send this event if:
a) the change is due to the creation of a namespace (refer to section 5.20); or
b) the change is due to the deletion of a namespace (refer to section 5.20),
as the Namespace Attribute Changed event is sent for these changes."
The Namespace Attribute Changed event has no way of notifying the host
of a creation of new ANA group, so strangely interpreting that entirely
different event to be part of the namespace creation does not make any
sense whatsover.
Creating the group at the spec level is not due to creating a namespace.
That might be the interpretation of your management backend and is an
ok implementation, but nothing in the spec implicitly creates groups as
part of namespaces creation.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-12-09 7:28 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201118114859.7985-1-marting@netapp.com>
2020-11-18 16:24 ` [PATCH] nvme-core: update NS Attr Changed AEN handling for ANA group Christoph Hellwig
2020-11-18 20:09 ` George, Martin
2020-11-20 9:44 ` hch
2020-11-23 14:35 ` Meneghini, John
2020-11-23 15:27 ` Knight, Frederick
2020-11-23 15:54 ` Meneghini, John
2020-12-07 15:25 ` hch
2020-12-08 15:21 ` Knight, Frederick
2020-12-08 17:40 ` Keith Busch
2020-12-08 18:15 ` Knight, Frederick
2020-12-08 18:34 ` Keith Busch
2020-12-08 19:13 ` Knight, Frederick
2020-12-08 21:46 ` Keith Busch
2020-12-09 0:07 ` Knight, Frederick
2020-12-09 0:20 ` Keith Busch
2020-12-09 7:26 ` Hannes Reinecke
2020-12-09 0:13 ` Knight, Frederick
2020-12-09 7:28 ` hch [this message]
2020-12-09 15:20 ` Knight, Frederick
2020-12-09 15:53 ` Keith Busch
2020-12-09 16:02 ` Hannes Reinecke
2020-12-09 16:19 ` Keith Busch
2020-12-09 17:04 ` Hannes Reinecke
2020-12-09 17:39 ` Keith Busch
2020-12-09 17:47 ` hch
2020-12-09 20:58 ` Knight, Frederick
2020-12-09 21:34 ` Keith Busch
2020-12-10 8:51 ` hch
2020-12-10 9:13 ` Hannes Reinecke
2020-12-10 13:34 ` Keith Busch
2021-01-14 3:09 ` Sagi Grimberg
2021-01-14 22:59 ` Knight, Frederick
2021-01-14 23:16 ` Keith Busch
2021-01-15 7:15 ` Hannes Reinecke
2020-11-23 17:36 ` Keith Busch
2020-11-23 19:16 ` Sagi Grimberg
2020-11-23 19:29 ` George, Martin
2020-11-23 19:43 ` Keith Busch
2020-11-26 16:16 ` George, Martin
2020-12-04 14:40 ` Hannes Reinecke
2020-11-18 16:51 ` Sagi Grimberg
2020-11-18 20:16 ` George, Martin
2020-11-20 9:46 ` Christoph Hellwig
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=20201209072806.GA10037@lst.de \
--to=hch@lst.de \
--cc=Frederick.Knight@netapp.com \
--cc=John.Meneghini@netapp.com \
--cc=Martin.George@netapp.com \
--cc=hare@suse.com \
--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 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.