From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <kbusch@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
Uday Shankar <ushankar@purestorage.com>,
linux-nvme@lists.infradead.org,
Prabhath Sajeepa <psajeepa@purestorage.com>,
Jens Axboe <axboe@fb.com>, Sagi Grimberg <sagi@grimberg.me>
Subject: Re: Native multipath across multiple subsystem NQNs
Date: Mon, 14 Feb 2022 09:12:52 +0100 [thread overview]
Message-ID: <20220214081252.GA18231@lst.de> (raw)
In-Reply-To: <20220212212221.GB1660900@dhcp-10-100-145-180.wdc.com>
On Sat, Feb 12, 2022 at 01:22:21PM -0800, Keith Busch wrote:
> On Sat, Feb 12, 2022 at 07:34:22AM +0100, Christoph Hellwig wrote:
> > The answer is neither. The fact that NVMe with ANA required namespaces
> > to be be attached to the same subsystem is good and important.
> > TPE 4034 is retrograde and completely broken in this respect and should
> > have never been ratifier. Please fix your storage system to export
> > virtual subsystems like everyone else and don't break the nice NVMe
> > architecture.
>
> If anything, the driver could check for duplicate namespace identifiers
> across subsystems so that we could warn about or prevent exposing them.
Yes, this has actually been something I've been wanting to do for a long
time.
next prev parent reply other threads:[~2022-02-14 8:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 22:07 Native multipath across multiple subsystem NQNs Uday Shankar
2022-02-12 6:34 ` Christoph Hellwig
2022-02-12 21:22 ` Keith Busch
2022-02-14 8:12 ` Christoph Hellwig [this message]
2022-02-25 0:15 ` Uday Shankar
2022-02-25 0:53 ` Randy Jennings
2022-03-01 11:08 ` Christoph Hellwig
[not found] ` <2A0F911A-7900-401F-B75B-7D0C2866C33A@netapp.com>
2022-03-03 10:41 ` Christoph Hellwig
2022-03-03 11:04 ` Adurthi, Prashanth
2022-03-03 11:13 ` 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=20220214081252.GA18231@lst.de \
--to=hch@lst.de \
--cc=axboe@fb.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=psajeepa@purestorage.com \
--cc=sagi@grimberg.me \
--cc=ushankar@purestorage.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 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.