Storage Performance Development Kit (SPDK)
 help / color / mirror / Atom feed
From: Tobias Oberstein <tobias.oberstein at gmail.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Ceph/Bluestore SPDK based backend?
Date: Tue, 07 Feb 2017 19:20:21 +0100	[thread overview]
Message-ID: <9ee92422-bd3f-b9dc-924d-7576abb4e052@gmail.com> (raw)
In-Reply-To: F81DFD1A-057C-487B-864B-A2ECCB283082@intel.com

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

Hi Nate,

Am 07.02.2017 um 14:03 schrieb Marushak, Nathan:
> Hi Tobias,
>
> There has been some work done in Bluestore for this. If you search "SPDK Bluestore" or something similar you'll see some links.

I was trying to find conclusive info on the net before - with no 
definite result though, eg, after reading (collegue of yours):

Accelerate Ceph via SPDK

http://7xweck.com1.z0.glb.clouddn.com/cephdaybeijing201608/04-SPDK%E5%8A%A0%E9%80%9FCeph-XSKY%20Bluestore%E6%A1%88%E4%BE%8B%E5%88%86%E4%BA%AB-%E6%89%AC%E5%AD%90%E5%A4%9C-%E7%8E%8B%E8%B1%AA%E8%BF%88.pdf

My understanding is:

Bluestore seems to introduce a proper block device abstraction within 
the Ceph OSD implementation.

And this new OSD internal block device abstraction is implemented for 
one, over regular Linux block devices (already a step forward from being 
forced to shuffle everything through a filesystem).

But what I couldn't find in above or on the net: is there a SPDK backed 
implementation of this new Bluestore OSD block device abstraction?

Do you have a link for me? I really tried to find it ..

> The impact to performance of Ceph was somewhat limited however. There are bottlenecks in the Ceph OSD.

Ok=( Any public avail info on that?

In general: having a SPDK+DPDK backed implementation of Ceph/OSD seems 
highly desirable with potentially big impact .. not?

Thanks for your reply!
Cheers,
/Tobias

>
> Thanks,
> Nate
>
> On Feb 7, 2017, at 5:20 AM, Andrey Kuzmin <andrey.v.kuzmin(a)gmail.com<mailto:andrey.v.kuzmin(a)gmail.com>> wrote:
>
> Not that I know of, and likely because it belongs to Ceph, not SPDK. SPDK goal is to enable applications to utilize NVMe flash more efficiently, not to provide a backend for each and every application out there.
>
> Regards,
> Andrey
>
> On Feb 7, 2017 14:03, "Tobias Oberstein" <tobias.oberstein(a)gmail.com<mailto:tobias.oberstein(a)gmail.com>> wrote:
> Hi,
>
> the 16.2 release added a Ceph RBD block device as a backend for SPDK applications. I am wondering about the inverse?
>
> As in: having Ceph RBD OSDs use SPDK to use NVMe flash as underlying block storage.
>
> There seems to be efforts with Ceph/Bluestore
>
> http://www.slideshare.net/sageweil1/bluestore-a-new-faster-storage-backend-for-ceph
>
> to allow OSDs use raw block devices as underlying storage (instead of Filestore, which shuffles everything through a filesystem).
>
> So put differently: is there a Ceph/Bluestore block device implementation using SPDK?
>
> Cheers,
> /Tobias
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org<mailto:SPDK(a)lists.01.org>
> https://lists.01.org/mailman/listinfo/spdk
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org<mailto:SPDK(a)lists.01.org>
> https://lists.01.org/mailman/listinfo/spdk
>
>
>
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk
>


             reply	other threads:[~2017-02-07 18:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-07 18:20 Tobias Oberstein [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-02-08 10:42 [SPDK] Ceph/Bluestore SPDK based backend? Andrey Kuzmin
2017-02-07 22:37 Tobias Oberstein
2017-02-07 18:54 Walker, Benjamin
2017-02-07 18:16 Andrey Kuzmin
2017-02-07 18:06 Tobias Oberstein
2017-02-07 13:03 Marushak, Nathan
2017-02-07 12:20 Andrey Kuzmin
2017-02-07 11:03 Tobias Oberstein

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=9ee92422-bd3f-b9dc-924d-7576abb4e052@gmail.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