From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============1694111112757745271==" MIME-Version: 1.0 From: Walker, Benjamin Subject: Re: [SPDK] bdev layer Date: Thu, 28 Jul 2016 20:22:53 +0000 Message-ID: <1469737371.2387.130.camel@intel.com> In-Reply-To: CABSNBDFFzM53O0BhqdVFWixZfQfAy0BJhN3bHReWtCmD9UxhDw@mail.gmail.com List-ID: To: spdk@lists.01.org --===============1694111112757745271== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable 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 > = > Can someone explain the target use case for this ? Is it provide block li= ke access using SPDK?=C2=A0 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 d= river. 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 --===============1694111112757745271==--