On 10/27/2016 11:03 AM, Kumaraparameshwaran Rathnavel wrote:
> I meant how do we specify the subsystem. It's not the namespace. We create devices and how do we specify the subsystem.
>
>
>
> Sent from my iPhone
>
>> On 27-Oct-2016, at 11:27 PM, Kumaraparameshwaran Rathnavel <krath(a)cloudsimple.com> wrote:
>>
>> Hi Guys,
>>
>> I have a doubt. There are RPC apis to create block devices basically aio and malloc. After adding the block devices from RPC how do you specify the subsystem for the block devices that are added. Is there any API to specify that the created block devices belong to a name space
>>
>> It's really urgent ! Need your help!
>> Thanking you,
>> Param
>>

Hi Param,

Adding block devices to the NVMe over Fabrics target via RPC is a 
two-step process.  First create the block device using the appropriate 
RPC for the block device type, e.g. construct_malloc_bdev, then create a 
subsystem to export one or more block devices using 
construct_nvmf_subsystem.  The subsystem must use Virtual mode if you 
would like to export bdevs rather than a direct NVMe controller.

You can find an example of how these RPCs interact in our automated test 
scripts, such as test/nvmf/fio/fio.sh.

Note that the construct_*_bdev interfaces were recently changed to 
report the name of the bdev that was created in the response.  This can 
be used to determine the namespaces (bdev names) passed to 
construct_nvmf_subsystem.

-- Daniel