From: Dongli Zhang <dongli.zhang@oracle.com>
To: <linux-nvme@lists.infradead.org>
Subject: How to setup nvme-loop with multipath
Date: Sun, 3 May 2020 13:14:25 -0700 (PDT) [thread overview]
Message-ID: <a3692e2f-c3a3-4d2a-8dc7-b49058e01347@default> (raw)
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'?
Thank you very much!
{
"hosts": [
{
"nqn": "hostnqn"
}
],
"ports": [
{
"addr": {
"adrfam": "",
"traddr": "",
"treq": "not specified",
"trsvcid": "",
"trtype": "loop"
},
"portid": 1,
"referrals": [],
"subsystems": [
"testnqn",
"testnqn2"
]
}
],
"subsystems": [
{
"allowed_hosts": [
"hostnqn"
],
"attr": {
"allow_any_host": "0"
},
"namespaces": [
{
"device": {
"nguid": "ef90689c-6c46-d44c-89c1-4067801309a8",
"path": "/home/test/disk1.img"
},
"enable": 1,
"nsid": 1
},
{
"device": {
"nguid": "ef90689c-6c46-d44c-89c1-4067801309a2",
"path": "/home/test/disk2.img"
},
"enable": 1,
"nsid": 2
}
],
"nqn": "testnqn"
},
{
"allowed_hosts": [
"hostnqn"
],
"attr": {
"allow_any_host": "0"
},
"namespaces": [
{
"device": {
"nguid": "ef90689c-6c46-d44c-89c1-4067801309a3",
"path": "/home/test/disk3.img"
},
"enable": 1,
"nsid": 1
}
],
"nqn": "testnqn2"
}
]
}
Dongli Zhang
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2020-05-03 20:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-03 20:14 Dongli Zhang [this message]
2020-05-06 6:30 ` How to setup nvme-loop with multipath Christoph Hellwig
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=a3692e2f-c3a3-4d2a-8dc7-b49058e01347@default \
--to=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