From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35731) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1faBCm-0005GH-Ct for qemu-devel@nongnu.org; Mon, 02 Jul 2018 22:38:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1faBCl-0008Bd-Ir for qemu-devel@nongnu.org; Mon, 02 Jul 2018 22:38:12 -0400 From: Fam Zheng Date: Tue, 3 Jul 2018 10:37:55 +0800 Message-Id: <20180703023758.14422-1-famz@redhat.com> Subject: [Qemu-devel] [PATCH v4 0/3] backup: Use copy offloading List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: qemu-block@nongnu.org, Fam Zheng , Stefan Hajnoczi , Kevin Wolf , Max Reitz , Jeff Cody 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