From: Fam Zheng <famz@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-block@nongnu.org, Peter Lieven <pl@kamp.de>,
Max Reitz <mreitz@redhat.com>,
Ronnie Sahlberg <ronniesahlberg@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-block] [RFC PATCH v2 1/7] block: Introduce API for copy offloading
Date: Fri, 27 Apr 2018 13:52:33 +0800 [thread overview]
Message-ID: <20180427055233.GB4217@lemon.usersys.redhat.com> (raw)
In-Reply-To: <20180426145702.GG30991@stefanha-x1.localdomain>
On Thu, 04/26 15:57, Stefan Hajnoczi wrote:
> On Wed, Apr 18, 2018 at 11:04:18AM +0800, Fam Zheng wrote:
> > diff --git a/block/io.c b/block/io.c
> > index bd9a19a9c4..d274e9525f 100644
> > --- a/block/io.c
> > +++ b/block/io.c
> > @@ -2826,3 +2826,94 @@ void bdrv_unregister_buf(BlockDriverState *bs, void *host)
> > bdrv_unregister_buf(child->bs, host);
> > }
> > }
> > +
> > +static int bdrv_co_copy_range_internal(BdrvChild *src,
>
> Please remember to use coroutine_fn for coroutines! This applies to the
> other functions in this patch too.
OK!
>
> > +int bdrv_co_copy_range(BdrvChild *src, uint64_t src_offset,
> > + BdrvChild *dst, uint64_t dst_offset,
> > + uint64_t bytes, BdrvRequestFlags flags)
> > +{
> > + BdrvTrackedRequest src_req, dst_req;
> > + BlockDriverState *src_bs = src->bs;
> > + BlockDriverState *dst_bs = dst->bs;
> > + int ret;
> > +
> > + bdrv_inc_in_flight(src_bs);
> > + bdrv_inc_in_flight(dst_bs);
> > + tracked_request_begin(&src_req, src_bs, src_offset,
> > + bytes, BDRV_TRACKED_READ);
> > + tracked_request_begin(&dst_req, dst_bs, dst_offset,
> > + bytes, BDRV_TRACKED_WRITE);
>
> Tracked requests and in-flight counters are only updated on root nodes.
> This is not how read/write works. Does drain work on an internal or
> leaf node with multiple parents?
Telling from how bdrv_do_drained_begin is implemented now (recursive both to
parents and children), I think it should work. But you are right this is
inconsistent with read/write code, it seems I could move this it to
bdrv_co_copy_range_internal.
>
> > diff --git a/include/block/block.h b/include/block/block.h
> > index cdec3639a3..72ac011b2b 100644
> > --- a/include/block/block.h
> > +++ b/include/block/block.h
> > @@ -604,4 +604,8 @@ bool bdrv_can_store_new_dirty_bitmap(BlockDriverState *bs, const char *name,
> > */
> > void bdrv_register_buf(BlockDriverState *bs, void *host, size_t size);
> > void bdrv_unregister_buf(BlockDriverState *bs, void *host);
> > +
> > +int bdrv_co_copy_range(BdrvChild *bs, uint64_t offset,
> > + BdrvChild *src, uint64_t src_offset,
> > + uint64_t bytes, BdrvRequestFlags flags);
>
> Please document this new block.h API.
OK.
>
> These arguments are in the wrong order! The first BdrvChild is the
> source and the second is the destination.
Right, will fix.
Fam
next prev parent reply other threads:[~2018-04-27 5:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 3:04 [Qemu-devel] [RFC PATCH v2 0/7] qemu-img convert with copy offloading Fam Zheng
2018-04-18 3:04 ` [Qemu-devel] [RFC PATCH v2 1/7] block: Introduce API for " Fam Zheng
2018-04-26 14:57 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2018-04-27 5:52 ` Fam Zheng [this message]
2018-04-18 3:04 ` [Qemu-devel] [RFC PATCH v2 2/7] raw: Implement " Fam Zheng
2018-04-26 14:57 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2018-04-18 3:04 ` [Qemu-devel] [RFC PATCH v2 3/7] qcow2: " Fam Zheng
2018-04-26 15:34 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2018-04-27 6:28 ` Fam Zheng
2018-04-18 3:04 ` [Qemu-devel] [RFC PATCH v2 4/7] file-posix: Implement bdrv_co_copy_range Fam Zheng
2018-05-03 9:25 ` Stefan Hajnoczi
2018-04-18 3:04 ` [Qemu-devel] [RFC PATCH v2 5/7] iscsi: Implement copy offloading Fam Zheng
2018-05-03 10:27 ` Stefan Hajnoczi
2018-05-09 6:30 ` Fam Zheng
2018-04-18 3:04 ` [Qemu-devel] [RFC PATCH v2 6/7] block-backend: Add blk_co_copy_range Fam Zheng
2018-05-03 10:28 ` Stefan Hajnoczi
2018-04-18 3:04 ` [Qemu-devel] [RFC PATCH v2 7/7] qemu-img: Convert with copy offloading Fam Zheng
2018-05-03 10:34 ` Stefan Hajnoczi
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=20180427055233.GB4217@lemon.usersys.redhat.com \
--to=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@gmail.com \
--cc=stefanha@gmail.com \
--cc=stefanha@redhat.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).