Storage Performance Development Kit (SPDK)
 help / color / mirror / Atom feed
From: Daniel Verkamp <daniel.verkamp at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Namespace
Date: Mon, 31 Oct 2016 15:21:39 -0700	[thread overview]
Message-ID: <c1915416-5d62-bb35-a292-ecc1857b9a91@intel.com> (raw)
In-Reply-To: 0AABC3D2-9618-4689-9C70-2F899C702958@cloudsimple.com

[-- Attachment #1: Type: text/plain, Size: 1482 bytes --]

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

             reply	other threads:[~2016-10-31 22:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-31 22:21 Daniel Verkamp [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-11-30 18:43 [SPDK] Namespace Kumaraparameshwaran Rathnavel
2016-10-27 18:03 Kumaraparameshwaran Rathnavel
2016-10-27 17:57 Kumaraparameshwaran Rathnavel

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=c1915416-5d62-bb35-a292-ecc1857b9a91@intel.com \
    --to=spdk@lists.01.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