From: Christoph Hellwig <hch@infradead.org>
To: Dongli Zhang <dongli.zhang@oracle.com>
Cc: linux-nvme@lists.infradead.org
Subject: Re: How to setup nvme-loop with multipath
Date: Tue, 5 May 2020 23:30:23 -0700 [thread overview]
Message-ID: <20200506063023.GA6928@infradead.org> (raw)
In-Reply-To: <a3692e2f-c3a3-4d2a-8dc7-b49058e01347@default>
On Sun, May 03, 2020 at 01:14:25PM -0700, Dongli Zhang wrote:
> Hi nvme developers,
>
> Would you please help confirm if it is feasible to support multi-path (indeed
> shared namespace as id->cmic is always set for nvme-over-fabric) for nvme-loop
> so that we would be able to have much more complex topology configuration for
> nvme multi-path.
>
> Below is my sample json file. While both disk1.img and disk2.img are belong to
> 'testnqn', disk3.img is belong to 'testnqn2'.
>
> Is there any way to have disk2.img as shared namespace used by both 'testnqn'
> and 'testnqn2'?
All the namespace are shared by default. Just run your connect command
line again and you get another path (just use a different traddr to
make sure duplicates aren't sorted out)
This is my simple test connect script:
---
et -e
set +x
HOSTNQN=nqn.2014-08.org.nvmexpress:NVMf:uuid:77dca664-0d3e-4f67-b8b2-04c70e3f991f
NQN=nqn.2014-08.org.nvmexpress:NVMf:uuid:77dca664-0d3e-4f67-b8b2-04c70e3f991d
echo "transport=loop,hostnqn=$HOSTNQN,nqn=$NQN" > /dev/nvme-fabrics
echo "transport=loop,hostnqn=$HOSTNQN,nqn=$NQN,traddr=192.168.7.68" > /dev/nvme-
fabrics
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-05-06 6:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-03 20:14 How to setup nvme-loop with multipath Dongli Zhang
2020-05-06 6:30 ` Christoph Hellwig [this message]
2020-05-06 18:14 ` Dongli Zhang
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=20200506063023.GA6928@infradead.org \
--to=hch@infradead.org \
--cc=dongli.zhang@oracle.com \
--cc=linux-nvme@lists.infradead.org \
/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