From: Alex Elder <elder@inktank.com>
To: ceph-devel@vger.kernel.org
Subject: [PATCH 0/2] rbd: separating mapping info from rbd_device
Date: Thu, 11 Oct 2012 08:42:07 -0700 [thread overview]
Message-ID: <5076E8CF.1060108@inktank.com> (raw)
The rbd device structure has up to now contained information about
the rbd image (and possibly snapshot id) that backs it as well as
the device interface it represents in Linux when it is mapped. In
order to add layering support we're going to want to separate the
mapping information from the image information more clearly. This
was begun recently but these two patches do the bulk of the movement
of the rest of the mapping-related fields.
-Alex
[PATCH 1/2] rbd: move dev_id and list links into mapping
[PATCH 2/2] rbd: move more stuff into mapping
next reply other threads:[~2012-10-11 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 15:42 Alex Elder [this message]
2012-10-11 15:43 ` [PATCH 1/2] rbd: move dev_id and list links into mapping Alex Elder
2012-10-11 15:43 ` [PATCH 2/2] rbd: move more stuff " Alex Elder
2012-10-22 13:07 ` [PATCH 0/2] rbd: separating mapping info from rbd_device Alex Elder
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=5076E8CF.1060108@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox