From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Shribman, Aidan" <aidan.shribman@sap.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] XBRLE page delta compression for live migration of large memory apps
Date: Wed, 22 Jun 2011 13:25:30 +0100 [thread overview]
Message-ID: <BANLkTim90CRW8-8H5ZT9k3xMc1d+_5bOzg@mail.gmail.com> (raw)
In-Reply-To: <4E01D9B3.8030002@codemonkey.ws>
On Wed, Jun 22, 2011 at 1:01 PM, Anthony Liguori <anthony@codemonkey.ws> wrote:
> On 05/22/2011 07:00 AM, Shribman, Aidan wrote:
>>
>> Subject: [PATCH] XBRLE page delta compression for live migration of large
>> memory apps
>> From: Aidan Shribman<aidan.shribman@sap.com>
>>
>> By using XBRLE (Xor Based Run-Length-Encoding) we can reduce required
>> bandwidth for transfering of dirty memory pages during live migration
>> migrate_set_cachesize<size>
>> migrate -x<url>
>> Qemu host: Ubuntu 10.10
>> Testing: live migration (w and w/o XBRLE) tested successfully.
>
> By how much?
>
> This is a change to the live migration protocol, it would also require
> documentation and an understanding of how it affects compatibility.
>
> The patch really needs to be split into logical pieces too. It's a bit too
> big for a meaningful review.
Two places where you could consider splitting the patch is the caching
and the sampling. Are they necessary for correctness and could they
be submitted as follow-up patches to a core patch which does just the
XBRLE?
Also, whenever there are heuristics and use of floating point then
there is some magic going on. It may be necessary and give a huge
performance boost but needs explanation so it is not a black box or
fragile mechanism once it has been merged upstream.
Stefan
next prev parent reply other threads:[~2011-06-22 12:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-22 12:00 [Qemu-devel] [PATCH] XBRLE page delta compression for live migration of large memory apps Shribman, Aidan
2011-06-13 13:10 ` Shribman, Aidan
2011-06-22 12:01 ` Anthony Liguori
2011-06-22 12:25 ` Stefan Hajnoczi [this message]
2011-07-06 12:04 ` Shribman, Aidan
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=BANLkTim90CRW8-8H5ZT9k3xMc1d+_5bOzg@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=aidan.shribman@sap.com \
--cc=qemu-devel@nongnu.org \
/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).