All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Elder <elder@inktank.com>
To: ceph-devel@vger.kernel.org
Subject: [PATCH 0/9] rbd: activate v2 image support
Date: Fri, 07 Sep 2012 16:09:07 -0500	[thread overview]
Message-ID: <504A6273.7030807@inktank.com> (raw)

This is the eight and final series of patches, this one finally
populating the code that implements support for rbd version 2
images in the Linux kernel rbd client.

All of the previous patches laid the ground work to make these
last steps pretty straightforward.  The first patch lays out
a mechanism where a request to map an rbd image results in a
"probe" operation to determine whether the named image exists
as either version 1 or version 2 format.  Once its existence
(and version) is determined, the rest of the setup for the
rbd device structure proceeds using code appropriate for the
image type.

The last patch in this series simply activates support for
version 2 images, by returning a success indication rather
than ENOSUPP from the version 2 probe routine.

The 7 patches bracketed by these two simply populate the code
that fetches information about a version 2 image, including
its snapshot context and the name and other information about
each snapshot.

This series is available as branch "wip-rbd-review-8" on the
ceph-client git repository, and is based on the branch
"wip-rbd-review-7".

    https://github.com/ceph/ceph-client/tree/wip-rbd-review-8

					-Alex

[PATCH 1/9]  17d4a86 rbd: lay out header probe infrastructure
[PATCH 2/9]  86dbebe rbd: add code to get the size of a v2 rbd image
[PATCH 3/9]  0e94833 rbd: get the object prefix for a v2 rbd image
[PATCH 4/9]  a0b250d rbd: get image features for a v2 image
[PATCH 5/9]  57b9193 rbd: get the snapshot context for a v2 image
[PATCH 6/9]  bd39e1f rbd: get snapshot name for a v2 image
[PATCH 7/9]  f33e41f rbd: update remaining header fields for v2
[PATCH 8/9]  431a5bd rbd: define rbd_dev_v2_snapc_refresh()
[PATCH 9/9]  c9c6c27 rbd: activate v2 image support

             reply	other threads:[~2012-09-07 21:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-07 21:09 Alex Elder [this message]
2012-09-07 21:13 ` [PATCH 1/9] rbd: lay out header probe infrastructure Alex Elder
2012-09-19 18:35   ` Josh Durgin
2012-09-07 21:13 ` [PATCH 2/9] rbd: add code to get the size of a v2 rbd image Alex Elder
2012-09-19 18:52   ` Josh Durgin
2012-09-07 21:13 ` [PATCH 3/9] rbd: get the object prefix for " Alex Elder
2012-09-19 18:57   ` Josh Durgin
2012-09-07 21:13 ` [PATCH 4/9] rbd: get image features for a v2 image Alex Elder
2012-09-19 19:02   ` Josh Durgin
2012-09-07 21:13 ` [PATCH 5/9] rbd: get the snapshot context " Alex Elder
2012-09-19 19:17   ` Josh Durgin
2012-09-07 21:14 ` [PATCH 6/9] rbd: get snapshot name " Alex Elder
2012-09-19 19:31   ` Josh Durgin
2012-09-07 21:15 ` [PATCH 7/9] rbd: update remaining header fields for v2 Alex Elder
2012-09-19 19:38   ` Josh Durgin
2012-09-07 21:15 ` [PATCH 8/9] rbd: define rbd_dev_v2_snapc_refresh() Alex Elder
2012-09-19 21:00   ` Josh Durgin
2012-09-07 21:15 ` [PATCH 9/9] rbd: activate v2 image support Alex Elder
2012-09-19 19:56   ` Josh Durgin
2012-09-19 19:57     ` 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=504A6273.7030807@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.