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] BDEV & VBDEV
Date: Fri, 21 Oct 2016 10:48:21 -0700	[thread overview]
Message-ID: <c41444c6-27f1-597b-89ba-9078d1fa7798@intel.com> (raw)
In-Reply-To: 64579C2D-E734-4D57-820F-B224400B2E37@cloudsimple.com

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

On 10/21/2016 06:31 AM, Kumaraparameshwaran Rathnavel wrote:
> Hi Guys,
>
> What is the difference between BDEV and VBDEV ?
>
> Thanking You,
> Param

Hi Param,

Regular bdevs expose raw block devices (NVMe namespaces, kernel block 
devices via libaio, etc.). They typically interface with a hardware 
device that needs to be polled periodically to check for completions.

A vbdev is a "virtual blockdev" that consumes one or more bdevs and 
produces another set of bdevs.  A vbdev can process each I/O and decide 
what to do with it - for example, it could send each I/O to an 
underlying bdev, or split a single request into multiple I/Os to several 
different bdevs to implement features like RAID, or even encrypt writes 
and decrypt reads to add a disk encryption layer.

We don't have any vbdev examples in the tree currently, but we plan to 
add an example vbdev that will read partition tables from a disk and 
expose each partition as another bdev that can be exposed as an iSCSI 
LUN or NVMe over Fabrics namespace.

Thanks,
-- Daniel

             reply	other threads:[~2016-10-21 17:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-21 17:48 Daniel Verkamp [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-10-22  4:51 [SPDK] BDEV & VBDEV Kumaraparameshwaran Rathnavel
2016-10-21 18:24 Daniel Verkamp
2016-10-21 17:59 Kumaraparameshwaran Rathnavel
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=c41444c6-27f1-597b-89ba-9078d1fa7798@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