From: Walker, Benjamin <benjamin.walker at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] bdev layer
Date: Thu, 28 Jul 2016 20:22:53 +0000 [thread overview]
Message-ID: <1469737371.2387.130.camel@intel.com> (raw)
In-Reply-To: CABSNBDFFzM53O0BhqdVFWixZfQfAy0BJhN3bHReWtCmD9UxhDw@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 815 bytes --]
On Tue, 2016-07-26 at 15:07 -0700, txcy uio wrote:
> Hello
>
>
> Recently the following was committed :
>
>
> bdev: add block device abstraction layer
> Change-Id: I235cf146a52714756c9782c03b118f518c5f5182
> Signed-off-by: Daniel Verkamp <daniel.verkamp(a)intel.com>
>
> Can someone explain the target use case for this ? Is it provide block like access using SPDK?
This is a generic translation layer that exposes a common "block-like" API we've defined and can
translate to a number of separate backends, including libaio and our NVMe driver. This library needs
quite a bit of work currently, but this is a start at least.
>
> --Tyc
>
>
>
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk
next reply other threads:[~2016-07-28 20:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 20:22 Walker, Benjamin [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-07-26 22:07 [SPDK] bdev layer txcy uio
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=1469737371.2387.130.camel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.