From: Alex Elder <elder@inktank.com>
To: ceph-devel@vger.kernel.org
Subject: [PATCH 00/11] rbd: layered read functionality
Date: Thu, 11 Apr 2013 21:14:39 -0500 [thread overview]
Message-ID: <51676E0F.2010504@inktank.com> (raw)
This series puts in place code that is able to handle
read requests on rbd clone images, forwarding them to
a parent snapshot image if necessary. Missing from this
series is a temporary patch at the end which actually
activates this functionality. That will not go in
until the rest of rbd layering functionality is in place.
I'm going to restate that. This code implements reads
for layered rbd images, but the functionality will not
be usable quite yet.
Most of the series is adding flags to image and object
requests, and putting in place some accounting in (parent)
image requests so it can be used to record the completion
of an object request that initiated it.
-Alex
[PATCH 01/11] rbd: record overall image request result
[PATCH 02/11] rbd: record aggregate image transfer count
[PATCH 03/11] rbd: record image-relative offset in object requests
[PATCH 04/11] rbd: define image request flags
[PATCH 05/11] rbd: define image request originator flag
[PATCH 06/11] rbd: define image request layered flag
[PATCH 07/11] rbd: encapsulate image object end request handling
[PATCH 08/11] rbd: define an rbd object request flags field
[PATCH 09/11] rbd: add an object request flag for image data objects
[PATCH 10/11] rbd: probe the parent of an image if present
[PATCH 11/11] rbd: implement layered reads
next reply other threads:[~2013-04-12 2:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 2:14 Alex Elder [this message]
2013-04-12 2:17 ` [PATCH 01/11] rbd: record overall image request result Alex Elder
2013-04-12 2:17 ` [PATCH 02/11] rbd: record aggregate image transfer count Alex Elder
2013-04-12 2:17 ` [PATCH 03/11] rbd: record image-relative offset in object requests Alex Elder
2013-04-12 2:17 ` [PATCH 04/11] rbd: define image request flags Alex Elder
2013-04-12 2:17 ` [PATCH 05/11] rbd: define image request originator flag Alex Elder
2013-04-12 2:18 ` [PATCH 06/11] rbd: define image request layered flag Alex Elder
2013-04-12 2:18 ` [PATCH 07/11] rbd: encapsulate image object end request handling Alex Elder
2013-04-12 2:18 ` [PATCH 08/11] rbd: define an rbd object request flags field Alex Elder
2013-04-12 2:18 ` [PATCH 09/11] rbd: add an object request flag for image data objects Alex Elder
2013-04-12 2:18 ` [PATCH 10/11] rbd: probe the parent of an image if present Alex Elder
2013-04-12 2:19 ` [PATCH 11/11] rbd: implement layered reads Alex Elder
2013-04-14 17:22 ` [PATCH 00/11] rbd: layered read functionality 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=51676E0F.2010504@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.