On Fri, Sep 22, 2017 at 08:21:09AM +0800, Tony Yang wrote:
> Excuse me,
>ask an junior question, how can you complete the nvme mpath package
> clone, I use git clone, after completion, found no nvme directory.
>
>
> [root@scst1 soft]# git clone
> git://git.infradead.org/users/hch/block.git
Excuse me,
ask an junior question, how can you complete the nvme mpath package
clone, I use git clone, after completion, found no nvme directory.
[root@scst1 soft]# git clone
git://git.infradead.org/users/hch/block.git nvme-mpath
Cloning into 'nvme-mpath'...
remote: Counting objects:
On Thu, Sep 21, 2017 at 07:23:45AM +0200, Johannes Thumshirn wrote:
> Ah OK, we maybe should update nvme-cli to recognize it as well then. I just
> looked at the output of nvme list and obviously didn't find it.
Overloading the new per-subsystem nodes into nvme list would be
very confusing I
On Wed, Sep 20, 2017 at 04:55:46PM +0200, Christoph Hellwig wrote:
> On Wed, Sep 20, 2017 at 01:09:59PM +0200, Johannes Thumshirn wrote:
> > Using your patchset and doing the sanme double connect trick I get the same
> > two block devices of cause.
> >
> > How do I connect using both paths?
>
>
Hi Christoph,
I wanted to test your patches, but I fail to see how I have to set it up.
I do have a host with two RDMA HCAs connected to the target (Linux), for "normal
dm-mpath" test I do nvme connect with the host traddr argument for both of the
HCAs and get two nvme block devices which I can
Hi all,
this series adds support for multipathing, that is accessing nvme
namespaces through multiple controllers to the nvme core driver.
It is a very thin and efficient implementation that relies on
close cooperation with other bits of the nvme driver, and few small
and simple block helpers.
