Thank you for your reply.
So is this just to limit the size of the dynamic controller pool?
I think the feature is good and you can submit patches.
Code will be freezed soon toward SPDK 21.04, and so review may be delayed though.
Hi Ben, Jim, Alexey,
Please give your feedback if you have.
差出人: Jonathan Teh <jonathan.teh(a)mayadata.io>
送信日時: 2021年4月9日 23:43
宛先: spdk(a)lists.01.org <spdk(a)lists.01.org>
件名: [SPDK] Re: NVMe Multipath subsystem controller IDs
On 08/04/2021 23:09, 松本周平 wrote:
Hi Jonathan, Ben,
I'm not an expert in this area but supporting multiple SPDK
instances is also important to iSCSI.
I see the value of per-subsystem controller ID range and it is already
added to Linux target.
But we have little auto test for multiple SPDK target instances.
Could you enhance test/nvmf/target/multitarget.sh to verify the feature?
To verify the controller ID range has changed, an initiator needs to
connect to the controller and a specified subsystem. For that, I added a
test to test/nvmf/target/nvme_cli.sh that extracts the controller ID
from the output of "nvme id-ctrl".
And do we have negative side effect if we support per-subsystem
Not really AFAIK, the more limited controller ID range means a lower
limit on the number of simultaneous connections to an individual
controller for a subsystem but there's typically only one connection anyway.
SPDK mailing list -- spdk(a)lists.01.org
To unsubscribe send an email to spdk-leave(a)lists.01.org