From: Josh Durgin <josh.durgin@inktank.com>
To: Alex Elder <elder@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: [PATCH] rbd: support reading parent page data for writes
Date: Sat, 11 May 2013 12:27:00 -0700 [thread overview]
Message-ID: <518E9B84.20100@inktank.com> (raw)
In-Reply-To: <518E81E1.2000806@inktank.com>
On 05/11/2013 10:37 AM, Alex Elder wrote:
> Currently, rbd_img_obj_parent_read_full() assumes the incoming
> object request contains bio data. But if a layered image is part of
> a multi-layer stack of images it will result in read requests of
> page data to parent images.
>
> This is handling the same kind of issue as was resolved by this
> commit:
> 5b2ab72d rbd: support reading parent page data
>
> This resolves:
> http://tracker.ceph.com/issues/5027
>
> Signed-off-by: Alex Elder <elder@inktank.com>
> ---
> drivers/block/rbd.c | 21 ++++++++++++++-------
> 1 file changed, 14 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/block/rbd.c b/drivers/block/rbd.c
> index 51c45e7..b9221a0 100644
> --- a/drivers/block/rbd.c
> +++ b/drivers/block/rbd.c
> @@ -2160,7 +2160,8 @@ rbd_img_obj_parent_read_full_callback(struct
> rbd_img_request *img_request)
> struct page **pages;
> int result;
> u64 obj_size;
> - u64 xferred;
> + u64 offset;
> + u64 length;
>
> rbd_assert(img_request_child_test(img_request));
>
> @@ -2172,10 +2173,10 @@ rbd_img_obj_parent_read_full_callback(struct
> rbd_img_request *img_request)
>
> orig_request = img_request->obj_request;
> rbd_assert(orig_request != NULL);
> - rbd_assert(orig_request->type == OBJ_REQUEST_BIO);
> + rbd_assert(obj_request_type_valid(orig_request->type));
> result = img_request->result;
> obj_size = img_request->length;
Naming this obj_size is a bit confusing now, since a parent read that
would cross the overlap point will be shortened to less than an object
size.
The rest looks good.
Reviewed-by: Josh Durgin <josh.durgin@inktank.com>
> - xferred = img_request->xferred;
> + rbd_assert(obj_size == img_request->xferred);
> rbd_img_request_put(img_request);
>
> rbd_assert(orig_request->img_request);
> @@ -2204,11 +2205,17 @@ rbd_img_obj_parent_read_full_callback(struct
> rbd_img_request *img_request)
>
> /* Then the original write request op */
>
> + offset = orig_request->offset;
> + length = orig_request->length;
> osd_req_op_extent_init(osd_req, 1, CEPH_OSD_OP_WRITE,
> - orig_request->offset,
> - orig_request->length, 0, 0);
> - osd_req_op_extent_osd_data_bio(osd_req, 1, orig_request->bio_list,
> - orig_request->length);
> + offset, length, 0, 0);
> + if (orig_request->type == OBJ_REQUEST_BIO)
> + osd_req_op_extent_osd_data_bio(osd_req, 1,
> + orig_request->bio_list, length);
> + else
> + osd_req_op_extent_osd_data_pages(osd_req, 1,
> + orig_request->pages, length,
> + offset & ~PAGE_MASK, false, false);
>
> rbd_osd_req_format_write(orig_request);
>
next prev parent reply other threads:[~2013-05-11 19:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-11 17:37 [PATCH] rbd: support reading parent page data for writes Alex Elder
2013-05-11 19:27 ` Josh Durgin [this message]
2013-05-13 17:58 ` [PATCH] rbd: fix parent request size assumption Alex Elder
2013-05-13 18:48 ` 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=518E9B84.20100@inktank.com \
--to=josh.durgin@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--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.