From: Stefan Hajnoczi <stefanha@redhat.com>
To: jemmy858585@gmail.com
Cc: qemu-devel@nongnu.org, famz@redhat.com, quintela@redhat.com,
dgilbert@redhat.com, qemu-block@nongnu.org,
Lidong Chen <lidongchen@tencent.com>
Subject: Re: [Qemu-devel] [PATCH v6] migration/block: use blk_pwrite_zeroes for each zero cluster
Date: Thu, 13 Apr 2017 15:16:17 +0100 [thread overview]
Message-ID: <20170413141617.GD13387@stefanha-x1.localdomain> (raw)
In-Reply-To: <1492050868-16200-1-git-send-email-lidongchen@tencent.com>
[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]
On Thu, Apr 13, 2017 at 10:34:28AM +0800, jemmy858585@gmail.com wrote:
> From: Lidong Chen <lidongchen@tencent.com>
>
> BLOCK_SIZE is (1 << 20), qcow2 cluster size is 65536 by default,
> this may cause the qcow2 file size to be bigger after migration.
> This patch checks each cluster, using blk_pwrite_zeroes for each
> zero cluster.
>
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
> Signed-off-by: Lidong Chen <lidongchen@tencent.com>
> ---
> v6 changelog:
> Fix up some grammar in the comment.
> ---
> migration/block.c | 35 +++++++++++++++++++++++++++++++++--
> 1 file changed, 33 insertions(+), 2 deletions(-)
I fixed the following gcc warning when merging the patch:
migration/block.c:958:25: error: ‘cluster_size’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
buffer_is_zero(cur_buf, cluster_size)) {
Thanks, applied to my block-next tree:
https://github.com/stefanha/qemu/commits/block-next
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2017-04-13 14:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 2:34 [Qemu-devel] [PATCH v6] migration/block: use blk_pwrite_zeroes for each zero cluster jemmy858585
2017-04-13 14:16 ` Stefan Hajnoczi [this message]
2017-04-14 0:57 ` 858585 jemmy
2017-04-14 6:00 ` Fam Zheng
2017-04-14 6:30 ` 858585 jemmy
2017-04-17 3:49 ` Fam Zheng
2017-04-17 4:00 ` 858585 jemmy
2017-04-24 7:40 ` 858585 jemmy
2017-04-24 11:54 ` 858585 jemmy
2017-04-24 12:09 ` Fam Zheng
2017-04-24 12:15 ` 858585 jemmy
2017-04-24 12:19 ` Fam Zheng
2017-04-24 12:26 ` 858585 jemmy
2017-04-24 12:36 ` Fam Zheng
2017-04-24 12:44 ` 858585 jemmy
2017-04-14 6:38 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2017-04-14 6:48 ` 858585 jemmy
2017-04-17 3:47 ` Fam Zheng
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=20170413141617.GD13387@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=dgilbert@redhat.com \
--cc=famz@redhat.com \
--cc=jemmy858585@gmail.com \
--cc=lidongchen@tencent.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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).