From: jemmy858585@gmail.com
To: qemu-devel@nongnu.org
Cc: stefanha@redhat.com, famz@redhat.com, quintela@redhat.com,
dgilbert@redhat.com, qemu-block@nongnu.org,
Lidong Chen <lidongchen@tencent.com>
Subject: [Qemu-devel] [PATCH v3] migration/block: use blk_pwrite_zeroes for each zero cluster
Date: Sun, 9 Apr 2017 20:37:40 +0800 [thread overview]
Message-ID: <1491741460-10308-1-git-send-email-lidongchen@tencent.com> (raw)
From: Lidong Chen <lidongchen@tencent.com>
BLOCK_SIZE is (1 << 20), qcow2 cluster size is 65536 by default,
this maybe cause the qcow2 file size is bigger after migration.
This patch check each cluster, use blk_pwrite_zeroes for each
zero cluster.
Signed-off-by: Lidong Chen <lidongchen@tencent.com>
---
migration/block.c | 38 ++++++++++++++++++++++++++++++++++++--
1 file changed, 36 insertions(+), 2 deletions(-)
diff --git a/migration/block.c b/migration/block.c
index 7734ff7..fe613db 100644
--- a/migration/block.c
+++ b/migration/block.c
@@ -885,6 +885,8 @@ static int block_load(QEMUFile *f, void *opaque, int version_id)
int64_t total_sectors = 0;
int nr_sectors;
int ret;
+ BlockDriverInfo bdi;
+ int cluster_size;
do {
addr = qemu_get_be64(f);
@@ -934,8 +936,40 @@ static int block_load(QEMUFile *f, void *opaque, int version_id)
} else {
buf = g_malloc(BLOCK_SIZE);
qemu_get_buffer(f, buf, BLOCK_SIZE);
- ret = blk_pwrite(blk, addr * BDRV_SECTOR_SIZE, buf,
- nr_sectors * BDRV_SECTOR_SIZE, 0);
+
+ ret = bdrv_get_info(blk_bs(blk), &bdi);
+ cluster_size = bdi.cluster_size;
+
+ if (ret == 0 && cluster_size > 0 &&
+ cluster_size <= BLOCK_SIZE &&
+ BLOCK_SIZE % cluster_size == 0) {
+ int i;
+ int64_t cur_addr;
+ uint8_t *cur_buf;
+
+ for (i = 0; i < BLOCK_SIZE / cluster_size; i++) {
+ cur_addr = addr * BDRV_SECTOR_SIZE
+ + i * cluster_size;
+ cur_buf = buf + i * cluster_size;
+
+ if (buffer_is_zero(cur_buf, cluster_size)) {
+ ret = blk_pwrite_zeroes(blk, cur_addr,
+ cluster_size,
+ BDRV_REQ_MAY_UNMAP);
+ } else {
+ ret = blk_pwrite(blk, cur_addr, cur_buf,
+ cluster_size, 0);
+ }
+
+ if (ret < 0) {
+ g_free(buf);
+ return ret;
+ }
+ }
+ } else {
+ ret = blk_pwrite(blk, addr * BDRV_SECTOR_SIZE, buf,
+ nr_sectors * BDRV_SECTOR_SIZE, 0);
+ }
g_free(buf);
}
--
1.8.3.1
next reply other threads:[~2017-04-09 12:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-09 12:37 jemmy858585 [this message]
2017-04-10 0:51 ` [Qemu-devel] [PATCH v3] migration/block: use blk_pwrite_zeroes for each zero cluster Fam Zheng
2017-04-10 1:10 ` 858585 jemmy
2017-04-10 1:44 ` Fam Zheng
2017-04-10 16:00 ` Stefan Hajnoczi
2017-04-11 1:19 ` 858585 jemmy
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=1491741460-10308-1-git-send-email-lidongchen@tencent.com \
--to=jemmy858585@gmail.com \
--cc=dgilbert@redhat.com \
--cc=famz@redhat.com \
--cc=lidongchen@tencent.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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).