linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Uday Shankar <ushankar@purestorage.com>
Cc: linux-nvme@lists.infradead.org,
	Prabhath Sajeepa <psajeepa@purestorage.com>,
	Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@fb.com>,
	Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>
Subject: Re: Native multipath across multiple subsystem NQNs
Date: Sat, 12 Feb 2022 07:34:22 +0100	[thread overview]
Message-ID: <20220212063422.GA16561@lst.de> (raw)
In-Reply-To: <20220211220714.GA370236@dev-ushankar.dev.purestorage.com>

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.


  reply	other threads:[~2022-02-12  6:34 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 [this message]
2022-02-12 21:22   ` Keith Busch
2022-02-14  8:12     ` Christoph Hellwig
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=20220212063422.GA16561@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 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).