From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============4387847693145542133==" MIME-Version: 1.0 From: Verkamp, Daniel Subject: Re: [SPDK] Nvmf target namespace specification Date: Fri, 04 May 2018 17:48:44 +0000 Message-ID: In-Reply-To: CANvN+enbJUk-hJWEKmzy9fvzg2zKhw4u_97LXUziRBR7-6r5=g@mail.gmail.com List-ID: To: spdk@lists.01.org --===============4387847693145542133== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Hi Andrey, Do you mean on the host (initiator) side, bdev/nvme? When you are connecti= ng to a NVMe-oF target with the NVMe bdev (either via the [Nvme] configurat= ion file section or the construct_nvme_bdev RPC method), you are specifying= the address to a subsystem, and all namespaces in that subsystem will be e= xposed as bdevs. There is currently no way to specify just a single namesp= ace within the subsystem, but we could probably add this if there is a reas= onable use case that requires it. If you are talking about the target side, you can configure namespaces to h= ave a particular ID using the optional second parameter to the Namespace li= ne in the [SubsystemN] config sections, or via the optional namespace.nsid = parameter to the nvmf_subsystem_add_ns RPC method. Thanks, -- Daniel > -----Original Message----- > From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Andrey Kuzmin > Sent: Friday, May 4, 2018 10:35 AM > To: Storage Performance Development Kit > Subject: [SPDK] Nvmf target namespace specification > = > Spdk nvmf docs suggest nvmf targets to be specified via > traddr/addrfam/traddr/trsvcid tuple. Is there any way to specify the > target controller namespace as well? > = > Regards, > Andrey > _______________________________________________ > SPDK mailing list > SPDK(a)lists.01.org > https://lists.01.org/mailman/listinfo/spdk --===============4387847693145542133==--