From: guangrong.xiao@gmail.com
To: pbonzini@redhat.com, mst@redhat.com, mtosatti@redhat.com
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, dgilbert@redhat.com,
peterx@redhat.com, wei.w.wang@intel.com, jiang.biao2@zte.com.cn,
eblake@redhat.com, quintela@redhat.com,
Xiao Guangrong <xiaoguangrong@tencent.com>
Subject: [Qemu-devel] [PATCH v6 0/3] migration: compression optimization
Date: Thu, 6 Sep 2018 15:00:58 +0800 [thread overview]
Message-ID: <20180906070101.27280-1-xiaoguangrong@tencent.com> (raw)
From: Xiao Guangrong <xiaoguangrong@tencent.com>
Changelog in v6:
Thanks to Juan's review, in this version we
1) move flush compressed data to find_dirty_block() where it hits the end
of memblock
2) use save_page_use_compression instead of migrate_use_compression in
flush_compressed_data
Xiao Guangrong (3):
migration: do not flush_compressed_data at the end of iteration
migration: show the statistics of compression
migration: use save_page_use_compression in flush_compressed_data
hmp.c | 13 +++++++++++
migration/migration.c | 12 ++++++++++
migration/ram.c | 63 +++++++++++++++++++++++++++++++++++++++++++--------
migration/ram.h | 1 +
qapi/migration.json | 26 ++++++++++++++++++++-
5 files changed, 105 insertions(+), 10 deletions(-)
--
2.14.4
next reply other threads:[~2018-09-06 7:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 7:00 guangrong.xiao [this message]
2018-09-06 7:00 ` [Qemu-devel] [PATCH v6 1/3] migration: do not flush_compressed_data at the end of iteration guangrong.xiao
2018-09-06 9:38 ` Juan Quintela
2018-09-06 7:01 ` [Qemu-devel] [PATCH v6 2/3] migration: show the statistics of compression guangrong.xiao
2018-09-06 7:01 ` [Qemu-devel] [PATCH v6 3/3] migration: use save_page_use_compression in flush_compressed_data guangrong.xiao
2018-09-06 9:49 ` Juan Quintela
2018-09-06 11:03 ` [Qemu-devel] [PATCH v6 0/3] migration: compression optimization Juan Quintela
2018-09-13 7:45 ` Xiao Guangrong
2018-09-13 13:26 ` Juan Quintela
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=20180906070101.27280-1-xiaoguangrong@tencent.com \
--to=guangrong.xiao@gmail.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=jiang.biao2@zte.com.cn \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=wei.w.wang@intel.com \
--cc=xiaoguangrong@tencent.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).