From: Alex Elder <elder@inktank.com>
To: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: [PATCH 0] rbd: layered writes
Date: Fri, 19 Apr 2013 17:52:18 -0500 [thread overview]
Message-ID: <5171CAA2.7000802@inktank.com> (raw)
In-Reply-To: <5171C963.2050402@inktank.com>
On 04/19/2013 05:46 PM, Alex Elder wrote:
> This set of patches culminates in providing layered
> write functionality for rbd clone images. Until the
> feature bits get enabled, most of this code is not
> yet activated. But it has been tested and it's
> ready for review. The feature will be enabled soon,
> after a few more things get cleaned up to prepare
> for it.
These patches are available in the "review/wip-copyup"
of the ceph-client git repository. They are based on
the branch "review/wip-4679-3" found there.
-Alex
>
> -Alex
>
> [PATCH] libceph: fix two messenger bugs
> Two bugs, two improvements.
>
> [PATCH] libceph: support pages for class request data
> This just defines a function that allows a page array
> to be specified for the data to be written by an
> object class method.
>
> [PATCH 1/4] rbd: define separate read and write format funcs
> [PATCH 2/4] rbd: encapsulate submission of image object requests
> [PATCH 3/4] rbd: define zero_pages()
> [PATCH 4/4] rbd: support page array image requests
> The first two of these are just cleanups. The second two
> add some functionality to allow image requests to use
> page arrays for their object data.
>
> [PATCH 1/2] rbd: implement full object parent reads
> [PATCH 2/2] rbd: issue a copyup for layered writes
> These last two finally implement the layered copyup
> functionality. The first is sort of a half step, to
> break up the review into smaller pieces.
>
prev parent reply other threads:[~2013-04-19 22:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 22:46 [PATCH 0] rbd: layered writes Alex Elder
2013-04-19 22:49 ` [PATCH] libceph: fix two messenger bugs Alex Elder
2013-04-22 7:14 ` Josh Durgin
2013-04-19 22:49 ` [PATCH] libceph: support pages for class request data Alex Elder
2013-04-22 7:15 ` Josh Durgin
2013-04-19 22:49 ` [PATCH 1/4] rbd: define separate read and write format funcs Alex Elder
2013-04-22 7:23 ` Josh Durgin
2013-04-19 22:50 ` [PATCH 2/4] rbd: encapsulate submission of image object requests Alex Elder
2013-04-22 7:35 ` Josh Durgin
2013-04-19 22:50 ` [PATCH 3/4] rbd: define zero_pages() Alex Elder
2013-04-22 8:05 ` Josh Durgin
2013-04-22 12:35 ` Alex Elder
2013-04-19 22:50 ` [PATCH 4/4] rbd: support page array image requests Alex Elder
2013-04-22 8:13 ` Josh Durgin
2013-04-19 22:50 ` [PATCH 1/2] rbd: implement full object parent reads Alex Elder
2013-04-22 18:13 ` Josh Durgin
2013-04-19 22:50 ` [PATCH 2/2] rbd: issue a copyup for layered writes Alex Elder
2013-04-22 18:16 ` Josh Durgin
2013-04-19 22:52 ` Alex Elder [this message]
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=5171CAA2.7000802@inktank.com \
--to=elder@inktank.com \
--cc=ceph-devel@vger.kernel.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 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.