From: Christoph Hellwig <hch@lst.de>
To: Anish M Jhaveri <anish.jhaveri@paviliondata.com>
Cc: sagi@grimberg.me, hch@lst.de, keith.busch@intel.com,
axboe@kernel.dk, linux-block@vger.kernel.org,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH 00/10] nvme multipath support on top of nvme-4.13 branch
Date: Fri, 15 Sep 2017 20:07:01 +0200 [thread overview]
Message-ID: <20170915180701.GA8981@lst.de> (raw)
In-Reply-To: <20170912042048.pdbyl6vsoeui6bnp@haynes>
Hi Anish,
I looked over the code a bit, and I'm rather confused by the newly
added commands. Which controller supports them? Also the NVMe
working group went down a very different way with the ALUA approch,
which uses different grouping concepts and doesn't require path
activations - for Linux we'd really like to stick to only standardized
multipath implementations.
WARNING: multiple messages have this Message-ID (diff)
From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 00/10] nvme multipath support on top of nvme-4.13 branch
Date: Fri, 15 Sep 2017 20:07:01 +0200 [thread overview]
Message-ID: <20170915180701.GA8981@lst.de> (raw)
In-Reply-To: <20170912042048.pdbyl6vsoeui6bnp@haynes>
Hi Anish,
I looked over the code a bit, and I'm rather confused by the newly
added commands. Which controller supports them? Also the NVMe
working group went down a very different way with the ALUA approch,
which uses different grouping concepts and doesn't require path
activations - for Linux we'd really like to stick to only standardized
multipath implementations.
next prev parent reply other threads:[~2017-09-15 18:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 4:20 [PATCH 00/10] nvme multipath support on top of nvme-4.13 branch Anish M Jhaveri
2017-09-12 4:20 ` Anish M Jhaveri
2017-09-13 6:57 ` Hannes Reinecke
2017-09-13 6:57 ` Hannes Reinecke
2017-09-19 4:40 ` anish.jhaveri
2017-09-19 4:40 ` anish.jhaveri
2017-09-15 18:07 ` Christoph Hellwig [this message]
2017-09-15 18:07 ` Christoph Hellwig
2017-09-19 5:10 ` Anish Jhaveri
2017-09-19 5:10 ` Anish Jhaveri
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=20170915180701.GA8981@lst.de \
--to=hch@lst.de \
--cc=anish.jhaveri@paviliondata.com \
--cc=axboe@kernel.dk \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.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.