From: Li Wang <liwang@ubuntukylin.com>
To: Cheng Cheng <ccheng.leo@gmail.com>
Cc: ceph-devel@vger.kernel.org, Sage Weil <sage@inktank.com>
Subject: Re: About the copy-on-read blueprint
Date: Fri, 05 Sep 2014 11:10:20 +0800 [thread overview]
Message-ID: <5409299C.4090801@ubuntukylin.com> (raw)
In-Reply-To: <CAC13JXaE0H8xh2rX2c+-x-c0jUGV+nKMuoG3Kg+8ZKj-TKTsFQ@mail.gmail.com>
This feature has been done and currently undergoing review
with its 3rd version. Nevertheless, we are pleasure to give any help.
BTW, Sage, Could you please take a little bit time to review the patch
we submitted one month ago.
Cheers,
Li Wang
On 2014/9/5 10:39, Cheng Cheng wrote:
> Hi Ceph Developers,
>
> I am just starting to use Ceph and find it is a great platform for
> hosting VM storage.
>
> As I want to dive further and learn more about Ceph, I want to take a
> starter task to familiarize myself with Ceph codebase. In particular,
> I found this copy-on-read is an interesting task
> (https://wiki.ceph.com/Planning/Sideboard/rbd%3A_copy-on-read_for_clones).
>
> However I find it is hard to get my hands dirty without mentorship. So
> I am wondering can anyone give me some bootstrap about how to
> contribute to Ceph and how to setup developing environment?
>
> Any help would be greatly appreciated!
>
> Sincerely,
> Cheng
> --
> 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:[~2014-09-05 3:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 20:02 Seeking for Mentor Cheng Cheng
2014-09-04 20:33 ` Loic Dachary
2014-09-05 3:10 ` Li Wang [this message]
2014-09-05 3:50 ` About the copy-on-read blueprint Cheng Cheng
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=5409299C.4090801@ubuntukylin.com \
--to=liwang@ubuntukylin.com \
--cc=ccheng.leo@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@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.