From: Josh Durgin <josh.durgin@dreamhost.com>
To: kvm@vger.kernel.org,
qemu-devel@nongnu.orgkvm@vger.kernel.orgqemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
ceph-devel@vger.kernel.org, Christian Brunner <chb@muc.de>
Subject: [Qemu-devel] [PATCH v5 0/4] rbd improvements
Date: Wed, 25 May 2011 13:34:43 -0700 [thread overview]
Message-ID: <1306355687-4647-1-git-send-email-josh.durgin@dreamhost.com> (raw)
This patchset moves the complexity of the rbd format into librbd and
adds truncation support.
Changes since v4:
* fixed cosmetic issues pointed out by Christian Brunner
Changes since v3:
* trivially rebased
* updated copyright header
Changes since v2:
* return values are checked in rbd_aio_rw_vector
* bdrv_truncate added
Josh Durgin (4):
rbd: use the higher level librbd instead of just librados
rbd: allow configuration of rados from the rbd filename
rbd: check return values when scheduling aio
rbd: Add bdrv_truncate implementation
block/rbd.c | 897 +++++++++++++++++++----------------------------------
block/rbd_types.h | 71 -----
configure | 33 +--
3 files changed, 335 insertions(+), 666 deletions(-)
delete mode 100644 block/rbd_types.h
--
1.7.2.3
next reply other threads:[~2011-05-25 20:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 20:34 Josh Durgin [this message]
2011-05-25 20:34 ` [Qemu-devel] [PATCH v5 1/4] rbd: use the higher level librbd instead of just librados Josh Durgin
2011-05-25 20:34 ` [Qemu-devel] [PATCH v5 2/4] rbd: allow configuration of rados from the rbd filename Josh Durgin
2011-05-26 8:13 ` Kevin Wolf
2011-05-26 23:06 ` Josh Durgin
2011-05-25 20:34 ` [Qemu-devel] [PATCH v5 3/4] rbd: check return values when scheduling aio Josh Durgin
2011-05-25 20:34 ` [Qemu-devel] [PATCH v5 4/4] rbd: Add bdrv_truncate implementation Josh Durgin
2011-05-26 8:05 ` Kevin Wolf
2011-05-26 23:09 ` Josh Durgin
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=1306355687-4647-1-git-send-email-josh.durgin@dreamhost.com \
--to=josh.durgin@dreamhost.com \
--cc=ceph-devel@vger.kernel.org \
--cc=chb@muc.de \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.orgkvm \
/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).