From: Kumaraparameshwaran Rathnavel <krath at cloudsimple.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] BDEV & VBDEV
Date: Sat, 22 Oct 2016 10:21:48 +0530 [thread overview]
Message-ID: <CDD0F3E1-9724-4536-B4D4-EE63439DB3FC@cloudsimple.com> (raw)
In-Reply-To: b3ba8aa6-c7d4-218b-c24b-76145ac2096c@intel.com
[-- Attachment #1: Type: text/plain, Size: 1368 bytes --]
My doubt is that we have malloc drives as virtual subsystem . So from NVMe initiator can I send read n write commands and does the current implementation of SPDK handle the commands and do the the I/O operations
Thanking you
Param
Sent from my iPhone
> On 21-Oct-2016, at 11:54 PM, Daniel Verkamp <daniel.verkamp(a)intel.com> wrote:
>
>> On 10/21/2016 10:59 AM, Kumaraparameshwaran Rathnavel wrote:
>> Thanks Daniel. So in the virtual subsystem the example in the tree is malloc devices. So instead of that I can create my own subsystem like malloc devices right. Is there support for virtual subsystem from end to end . Say that when I get a read command from kernel initiator the SPDK reads the data n then sends it back to the initiator
>>
>> Thanking you,
>> Param
>
> The nvmf_tgt "Virtual" mode (use bdevs as namespaces) is an alternative to "Direct" mode (expose hardware NVMe device directly). It is unrelated to the virtual blockdev layering mechanism. Any blockdev (regular bdev or vbdev) can be used as a namespace in nvmf_tgt Virtual mode.
>
> I'm not sure if I understand the rest of the question - can you elaborate on what you are trying to accomplish?
>
> Thanks,
> -- Daniel
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk
next reply other threads:[~2016-10-22 4:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-22 4:51 Kumaraparameshwaran Rathnavel [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-21 18:24 [SPDK] BDEV & VBDEV Daniel Verkamp
2016-10-21 17:59 Kumaraparameshwaran Rathnavel
2016-10-21 17:48 Daniel Verkamp
2016-10-21 13:31 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=CDD0F3E1-9724-4536-B4D4-EE63439DB3FC@cloudsimple.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