qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Jeff Cody <jcody@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
	Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 0/2] backup: Use copy offloading
Date: Mon, 2 Jul 2018 17:04:20 +0800	[thread overview]
Message-ID: <20180702090420.GO26002@lemon.usersys.redhat.com> (raw)
In-Reply-To: <20180605140631.4696-1-famz@redhat.com>

Jeff: ping? Can we have this in 3.0?

On Tue, 06/05 22:06, Fam Zheng wrote:
> Based-on: <20180529055959.32002-1-famz@redhat.com>
> ([PATCH v7 00/10] qemu-img convert with copy offloading)
> 
> 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 (2):
>   block: Honour BDRV_REQ_NO_SERIALISING in copy range
>   backup: Use copy offloading
> 
>  block/backup.c        | 150 ++++++++++++++++++++++++++++++------------
>  block/io.c            |   6 +-
>  block/trace-events    |   1 +
>  include/block/block.h |   5 +-
>  4 files changed, 117 insertions(+), 45 deletions(-)
> 
> -- 
> 2.17.0
> 

  parent reply	other threads:[~2018-07-02  9:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-05 14:06 [Qemu-devel] [PATCH v3 0/2] backup: Use copy offloading Fam Zheng
2018-06-05 14:06 ` [Qemu-devel] [PATCH v3 1/2] block: Honour BDRV_REQ_NO_SERIALISING in copy range Fam Zheng
2018-06-05 14:06 ` [Qemu-devel] [PATCH v3 2/2] backup: Use copy offloading Fam Zheng
2018-06-07 12:45 ` [Qemu-devel] [PATCH v3 0/2] " Stefan Hajnoczi
2018-07-02  9:04 ` Fam Zheng [this message]
2018-07-02 12:02   ` Jeff Cody

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=20180702090420.GO26002@lemon.usersys.redhat.com \
    --to=famz@redhat.com \
    --cc=jcody@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).