From: Jeff Cody <jcody@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
Stefan Hajnoczi <stefanha@redhat.com>,
Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 0/3] backup: Use copy offloading
Date: Mon, 2 Jul 2018 23:25:06 -0400 [thread overview]
Message-ID: <20180703032506.GB4184563@localhost.localdomain> (raw)
In-Reply-To: <20180703023758.14422-1-famz@redhat.com>
On Tue, Jul 03, 2018 at 10:37:55AM +0800, Fam Zheng wrote:
> v4: Rebase to master.
> Pick up Stefan's rev-bys.
> Include a block/io.c fix to fix a new issue caused by recent block/io.c
> change - our drive-backup cases in iotests exposes the bug loudly.
>
> This enhances the backup job to make use of the copy offloading API. It
> eliminates the necessity to use the bounce buffer as well as speeding up the
> copy operation when the backend supports it.
>
> v3: Don't forget coroutine_fn. [Stefan]
> Don't reset job->use_copy_range redundantly. [Stefan]
>
> v2: Use helper functions. [Stefan]
>
> Fam Zheng (3):
> block: Fix parameter checking in bdrv_co_copy_range_internal
> block: Honour BDRV_REQ_NO_SERIALISING in copy range
> backup: Use copy offloading
>
> block/backup.c | 150 ++++++++++++++++++++++++++++++------------
> block/io.c | 35 +++++-----
> block/trace-events | 1 +
> include/block/block.h | 5 +-
> 4 files changed, 132 insertions(+), 59 deletions(-)
>
> --
> 2.17.1
>
Thanks,
Applied to my block branch:
git://github.com/codyprime/qemu-kvm-jtc block
-Jeff
prev parent reply other threads:[~2018-07-03 3:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 2:37 [Qemu-devel] [PATCH v4 0/3] backup: Use copy offloading Fam Zheng
2018-07-03 2:37 ` [Qemu-devel] [PATCH v4 1/3] block: Fix parameter checking in bdrv_co_copy_range_internal Fam Zheng
2018-07-03 3:23 ` Jeff Cody
2018-07-03 2:37 ` [Qemu-devel] [PATCH v4 2/3] block: Honour BDRV_REQ_NO_SERIALISING in copy range Fam Zheng
2018-07-03 2:37 ` [Qemu-devel] [PATCH v4 3/3] backup: Use copy offloading Fam Zheng
2018-07-03 3:25 ` Jeff Cody [this message]
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=20180703032506.GB4184563@localhost.localdomain \
--to=jcody@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--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).