From: Jason Dillaman <jdillama@redhat.com>
To: Alexandre DERUMIER <aderumier@odiso.com>
Cc: jazeltq <jazeltq@gmail.com>, Tiger Hu <hufh2004@gmail.com>,
Josh Durgin <jdurgin@redhat.com>, Jeff Cody <jcody@redhat.com>,
Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>,
qemu-block@nongnu.org, qemu-devel <qemu-devel@nongnu.org>,
ceph-devel <ceph-devel@vger.kernel.org>,
tianqing <tianqing@unitedstack.com>
Subject: Re: [Qemu-devel] [RFC v5] RBD: Add support readv,writev for rbd
Date: Thu, 16 Feb 2017 10:26:13 -0500 [thread overview]
Message-ID: <CA+aFP1BuRC73WuWo=cS1XRAM=K+in6ac8WFPU26LVN+zdHWq=g@mail.gmail.com> (raw)
In-Reply-To: <887093105.8854266.1487258021988.JavaMail.zimbra@oxygem.tv>
On Thu, Feb 16, 2017 at 10:13 AM, Alexandre DERUMIER
<aderumier@odiso.com> wrote:
> Hi, I would like to bench it with small 4k read/write.
>
> On the ceph side,do we need this PR ? :
> https://github.com/ceph/ceph/pull/13447
Yes, that is the correct PR for the client-side librbd changes. You
should be able to test it against Hammer/Jewel-release clusters.
--
Jason
next prev parent reply other threads:[~2017-02-16 15:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-21 10:59 [Qemu-devel] [RFC v3] RBD: Add support readv,writev for rbd jazeltq
2017-01-21 11:13 ` no-reply
2017-01-21 13:19 ` [Qemu-devel] [RFC v4] " jazeltq
2017-02-16 8:43 ` jazeltq
2017-02-16 9:00 ` [Qemu-devel] [RFC v5] " jazeltq
2017-02-16 12:07 ` Tiger Hu
2017-02-16 14:03 ` Jaze Lee
2017-02-16 15:13 ` Alexandre DERUMIER
2017-02-16 15:26 ` Jason Dillaman [this message]
2017-02-16 14:14 ` Jason Dillaman
2017-02-16 14:22 ` Jaze Lee
2017-02-16 15:45 ` Eric Blake
2017-02-16 15:51 ` Jeff Cody
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='CA+aFP1BuRC73WuWo=cS1XRAM=K+in6ac8WFPU26LVN+zdHWq=g@mail.gmail.com' \
--to=jdillama@redhat.com \
--cc=aderumier@odiso.com \
--cc=ceph-devel@vger.kernel.org \
--cc=dillaman@redhat.com \
--cc=hufh2004@gmail.com \
--cc=jazeltq@gmail.com \
--cc=jcody@redhat.com \
--cc=jdurgin@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=tianqing@unitedstack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).