ceph-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Min Chen <minchen@ubuntukylin.com>
To: josh.durgin@inktank.com
Cc: ceph-devel@vger.kernel.org
Subject: [PATCH 0/3] librbd copy-on-read v2
Date: Tue, 13 May 2014 17:12:12 +0800	[thread overview]
Message-ID: <cover.1399970127.git.minchen@ubuntukylin.com> (raw)

summary:
  Rbd clone shares objects with its parent, unless writing data to clone. When read data from clone, it copy data from its parent if
object doesn't exits in clone. Each time read the same object(not in clone), the clone must send request to its parent. Usually the network latency
is bottleneck of read performance. If store the object into clone after copyup it from parent, then the next time read the same object
just in clone, which can improve read performance.
  Copy entire object from parent,no matter read entire or part of object.

Min Chen (3):
  librbd: copy-on-read for clones, add an option for copy-on-read
  librbd: copy-on-read for clones, read entire object from parent
  librbd: copy-on-read for clones, write entire object into child
    asychronously

 src/common/config_opts.h |    1 +
 src/include/xlist.h      |    1 +
 src/librbd/AioRequest.cc |   88 ++++++++++++++++++++++++++++++++++++++++++++--
 src/librbd/AioRequest.h  |    4 +++
 src/librbd/ImageCtx.cc   |   68 +++++++++++++++++++++++++++++++++++
 src/librbd/ImageCtx.h    |    6 ++++
 src/librbd/internal.cc   |    4 +++
 7 files changed, 169 insertions(+), 3 deletions(-)

-- 
1.7.10.4


             reply	other threads:[~2014-05-13  9:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13  9:12 Min Chen [this message]
2014-05-13  9:12 ` [PATCH 1/3] *v2* librbd: copy-on-read for clones, add an option for copy-on-read Min Chen
2014-05-13  9:12 ` [PATCH 2/3] *v2* librbd: copy-on-read for clones, read entire object from parent Min Chen
2014-05-13  9:12 ` [PATCH 3/3] *v2* librbd: copy-on-read for clones, write entire object into child asychronously Min Chen

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=cover.1399970127.git.minchen@ubuntukylin.com \
    --to=minchen@ubuntukylin.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=josh.durgin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).