All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Durgin <jdurgin@redhat.com>
To: Jens Axboe <axboe@kernel.dk>, Mark Nelson <mnelson@redhat.com>,
	"James (Fei) Liu-SSI" <james.liu@ssi.samsung.com>,
	Casey Bodley <cbodley@gmail.com>
Cc: Haomai Wang <haomaiwang@gmail.com>,
	"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
	daniel.gollub@gmail.com
Subject: Re: About Fio backend with ObjectStore API
Date: Tue, 30 Jun 2015 16:21:19 -0700	[thread overview]
Message-ID: <5593246F.2030201@redhat.com> (raw)
In-Reply-To: <559323CC.1000003@redhat.com>

On 06/30/2015 04:18 PM, Josh Durgin wrote:
> Note that ceph's ObjectStore api is internal, and not stable. Maybe not
> the best thing to include in packages, though keeping it as an option
> at build time might make sense. The api itself isn't that prone to
> change, but internal symbols (hooray c++...) certainly are, so any
> update of ceph would likely need a recompile of the backend.

And now I see the ObjectStore is included statically, so it is doable.
It just won't be updated for new ceph without recompiling the backend,
which seems fine to me.

>
> Josh
>
> On 06/30/2015 03:57 PM, Jens Axboe wrote:
>> I'd be more than happy to include it. Daniel has contributed to fio
>> before.
>>
>> Daniel (CC'ed), was it your intent to get this upstream? How do we make
>> this happen?


  reply	other threads:[~2015-06-30 23:21 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-30 16:05 About Fio backend with ObjectStore API Haomai Wang
2015-06-30 18:31 ` James (Fei) Liu-SSI
2015-06-30 21:15   ` Casey Bodley
2015-06-30 21:19     ` James (Fei) Liu-SSI
2015-06-30 22:38       ` Mark Nelson
2015-06-30 22:57         ` Jens Axboe
2015-06-30 23:18           ` Josh Durgin
2015-06-30 23:21             ` Josh Durgin [this message]
     [not found]           ` <CAHAfqgPMyfVtYrAp8ox11uA=q+zEDKP7Zoc2WveuYat=0hD8zg@mail.gmail.com>
2015-07-07  8:17             ` Haomai Wang
2015-07-07 17:25               ` James (Fei) Liu-SSI
2015-07-09  0:02       ` James (Fei) Liu-SSI
2015-07-09 16:19         ` Casey Bodley
2015-07-09 18:01           ` James (Fei) Liu-SSI
2015-07-09 19:32             ` Casey Bodley
2015-07-09 20:21               ` James (Fei) Liu-SSI
2015-07-09 20:26                 ` Matt W. Benjamin
2015-07-10  7:51                   ` Haomai Wang
2015-07-14  6:45                     ` Haomai Wang
2015-07-15 21:23                       ` Casey Bodley
2015-07-21 11:50                         ` Haomai Wang
2015-07-22 20:56                           ` Casey Bodley
2015-07-23  1:07                             ` Haomai Wang
2015-09-03  0:06                               ` James (Fei) Liu-SSI
2015-09-03 17:43                                 ` Casey Bodley
2015-09-04 20:29                                   ` James (Fei) Liu-SSI
2015-09-05  3:43                                     ` Haomai Wang
2015-09-11  0:08                                       ` James (Fei) Liu-SSI
2015-09-11 14:28                                         ` Casey Bodley
2015-09-11 14:35                                           ` Casey Bodley
2015-09-11 17:18                                           ` James (Fei) Liu-SSI
2015-09-11 20:08                                             ` Casey Bodley
2015-09-12  9:04                                               ` Haomai Wang
2015-09-12  9:16                                                 ` Haomai Wang
2015-09-15  0:02                                                   ` James (Fei) Liu-SSI
2015-09-12 23:23                                             ` Matt Benjamin
     [not found]                                   ` <99767EA2E27DD44DB4E9F9B9ACA458C03BD7AC7A@SSIEXCH-MB3.ssi.samsung.com>
     [not found]                                     ` <CACJqLyapDJ+H54fAeOVaWNh4DQHJkMVXbRXrzys08QNuCcXskw@mail.gmail.com>
2015-09-09 21:48                                       ` James (Fei) Liu-SSI

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=5593246F.2030201@redhat.com \
    --to=jdurgin@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=cbodley@gmail.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=daniel.gollub@gmail.com \
    --cc=haomaiwang@gmail.com \
    --cc=james.liu@ssi.samsung.com \
    --cc=mnelson@redhat.com \
    /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.