From: Josh Durgin <josh.durgin@inktank.com>
To: "Cláudio Martins" <ctpm@ist.utl.pt>
Cc: ceph-devel@vger.kernel.org, elder@inktank.com
Subject: Re: [PATCH 0/4] rbd: finish up basic format 2 support
Date: Wed, 10 Oct 2012 09:29:00 -0700 [thread overview]
Message-ID: <5075A24C.1080008@inktank.com> (raw)
In-Reply-To: <20121010165510.fc07422a.ctpm@ist.utl.pt>
On 10/10/2012 08:55 AM, Cláudio Martins wrote:
>
> On Tue, 09 Oct 2012 13:57:09 -0700 Alex Elder <elder@inktank.com> wrote:
>> This series includes updates for two patches posted previously.
>>
>> -Alex
>
> Greetings,
>
> We're gearing up to test v0.52 (specifically the RBD stuff) on our
> cluster. After reading this series of posts about rbd format 2 patches
> I began wondering if we should start testing these patches as well or
> not. To put it simply, what I'd like to know is:
>
> Is it enough to use the 3.6 vanilla kernel client to take full
> advantage of the rbd changes in v0.52 (i.e. new RBD cloning features)?
>
> Do we have any benefits from applying any of these patches on top of
> v3.6 and using "format 2", assuming that we stick to v0.52 on the
> server, or is this strictly v0.53 and beyond stuff?
>
>
> I apologize if this is a dumb question, but by looking at the v0.52
> changelog, at doc/rbd/* and the list, it doesn't seem clear how this
> fits with v0.52.
>
> Thanks in advance
>
> Best regards
>
> Cláudio
These patches support using format 2, to make adding new features
easy, but this is not very useful to you yet. They don't yet support
any new features (like cloning) - that's the next step, but it will
take a bunch more work.
To use rbd cloning, you'll need to access rbd through userspace (e.g.
with qemu and librbd) for now.
Josh
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-10-10 16:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 20:57 [PATCH 0/4] rbd: finish up basic format 2 support Alex Elder
2012-10-09 21:00 ` [PATCH 1/4] rbd: define rbd_update_size() Alex Elder
2012-10-09 23:27 ` Josh Durgin
2012-10-09 23:46 ` Alex Elder
2012-10-10 1:14 ` [PATCH 1/4, v2] rbd: define rbd_update_mapping_size() Alex Elder
2012-10-10 1:17 ` Josh Durgin
2012-10-09 21:00 ` [PATCH 2/4, v2] rbd: define rbd_dev_v2_refresh() Alex Elder
2012-10-09 23:30 ` Josh Durgin
2012-10-09 21:01 ` [PATCH 3/4] rbd: implement feature checks Alex Elder
2012-10-09 23:31 ` Josh Durgin
2012-10-09 21:01 ` [PATCH 4/4] rbd: activate v2 image support Alex Elder
2012-10-09 23:32 ` Josh Durgin
2012-10-10 15:55 ` [PATCH 0/4] rbd: finish up basic format 2 support Cláudio Martins
2012-10-10 16:29 ` Josh Durgin [this message]
2013-08-15 11:42 ` rbd: format 2 support in rbd.ko ? Kasper Dieter
2013-08-15 12:30 ` Damien Churchill
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=5075A24C.1080008@inktank.com \
--to=josh.durgin@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=ctpm@ist.utl.pt \
--cc=elder@inktank.com \
/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.