From: Xiao Guangrong <guangrong.xiao@gmail.com>
To: quintela@redhat.com
Cc: kvm@vger.kernel.org, mst@redhat.com, mtosatti@redhat.com,
Xiao Guangrong <xiaoguangrong@tencent.com>,
dgilbert@redhat.com, peterx@redhat.com, qemu-devel@nongnu.org,
wei.w.wang@intel.com, jiang.biao2@zte.com.cn,
pbonzini@redhat.com
Subject: Re: [PATCH v5 1/4] migration: do not flush_compressed_data at the end of each iteration
Date: Tue, 4 Sep 2018 12:00:25 +0800 [thread overview]
Message-ID: <05a122a4-de67-0c84-1f31-d767f24914c2@gmail.com> (raw)
In-Reply-To: <f22690e3-63d0-16e5-b2bc-de29471d3d0b@gmail.com>
On 09/04/2018 11:54 AM, Xiao Guangrong wrote:
>
> We will call it only if xbzrle is also enabled, at this case, we will
> disable compression and xbzrle for the following pages, please refer
^and use xbzrle
Sorry for the typo.
WARNING: multiple messages have this Message-ID (diff)
From: Xiao Guangrong <guangrong.xiao@gmail.com>
To: quintela@redhat.com
Cc: pbonzini@redhat.com, mst@redhat.com, mtosatti@redhat.com,
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, Xiao Guangrong <xiaoguangrong@tencent.com>
Subject: Re: [Qemu-devel] [PATCH v5 1/4] migration: do not flush_compressed_data at the end of each iteration
Date: Tue, 4 Sep 2018 12:00:25 +0800 [thread overview]
Message-ID: <05a122a4-de67-0c84-1f31-d767f24914c2@gmail.com> (raw)
In-Reply-To: <f22690e3-63d0-16e5-b2bc-de29471d3d0b@gmail.com>
On 09/04/2018 11:54 AM, Xiao Guangrong wrote:
>
> We will call it only if xbzrle is also enabled, at this case, we will
> disable compression and xbzrle for the following pages, please refer
^and use xbzrle
Sorry for the typo.
next prev parent reply other threads:[~2018-09-04 4:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 9:26 [PATCH v5 0/4] migration: compression optimization guangrong.xiao
2018-09-03 9:26 ` [Qemu-devel] " guangrong.xiao
2018-09-03 9:26 ` [PATCH v5 1/4] migration: do not flush_compressed_data at the end of each iteration guangrong.xiao
2018-09-03 9:26 ` [Qemu-devel] " guangrong.xiao
2018-09-03 16:38 ` Juan Quintela
2018-09-03 16:38 ` [Qemu-devel] " Juan Quintela
2018-09-04 3:54 ` Xiao Guangrong
2018-09-04 3:54 ` [Qemu-devel] " Xiao Guangrong
2018-09-04 4:00 ` Xiao Guangrong [this message]
2018-09-04 4:00 ` Xiao Guangrong
2018-09-04 9:28 ` Juan Quintela
2018-09-04 9:28 ` [Qemu-devel] " Juan Quintela
2018-09-03 9:26 ` [PATCH v5 2/4] migration: fix calculating xbzrle_counters.cache_miss_rate guangrong.xiao
2018-09-03 9:26 ` [Qemu-devel] " guangrong.xiao
2018-09-03 17:19 ` Juan Quintela
2018-09-03 17:19 ` [Qemu-devel] " Juan Quintela
2018-09-03 9:26 ` [PATCH v5 3/4] migration: show the statistics of compression guangrong.xiao
2018-09-03 9:26 ` [Qemu-devel] " guangrong.xiao
2018-09-03 17:22 ` Juan Quintela
2018-09-03 17:22 ` [Qemu-devel] " Juan Quintela
2018-09-03 9:26 ` [PATCH v5 4/4] migration: handle the error condition properly guangrong.xiao
2018-09-03 9:26 ` [Qemu-devel] " guangrong.xiao
2018-09-03 17:28 ` Juan Quintela
2018-09-03 17:28 ` [Qemu-devel] " 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=05a122a4-de67-0c84-1f31-d767f24914c2@gmail.com \
--to=guangrong.xiao@gmail.com \
--cc=dgilbert@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.