qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: Blue Swirl <blauwirbel@gmail.com>,
	Stefan Hajnoczi <stefanha@gmail.com>,
	"Shribman, Aidan" <aidan.shribman@sap.com>,
	qemu-devel Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v4] XBZRLE delta for live migration of large memory apps
Date: Mon, 08 Aug 2011 10:10:50 -0500	[thread overview]
Message-ID: <4E3FFC7A.3090000@codemonkey.ws> (raw)
In-Reply-To: <4E3FF705.9080009@redhat.com>

On 08/08/2011 09:47 AM, Avi Kivity wrote:
> On 08/08/2011 05:46 PM, Avi Kivity wrote:
>>
>> Please provide documentation in docs/ of the compression format.
>>
>> IMO it should be disabled by default (with an option to disable it,
>> via, sat, migrate-set-options, so we can migrate to older hosts).
>>
>> The protocol should allow XBZRLE to turn itself off if it detects that
>> it isn't effective.
>>
>
> IOW, this should be part of the standard migration protocol, not some
> side option that is enabled if the user remembers. It should not be
> mutually exclusive with future migration extensions, including compression.

Are you thinking of a static decision or a dynamic decision?

I think feature negotiation would address static decision making.  For 
dynamic decision making, you could look to something like the VNC 
protocol and how it encodes pixel data.  The flow looks something like:

1) All clients/servers must support raw encoding

2) Client presents list of support encodings

3) Server takes intersection of client supported encodings and server 
supported encodings.

4) Server can choose to encode updates using any encoding supported by 
client and server.

Regards,

Anthony Liguori

  parent reply	other threads:[~2011-08-08 15:11 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-08  8:42 [Qemu-devel] [PATCH v4] XBZRLE delta for live migration of large memory apps Shribman, Aidan
2011-08-08 13:29 ` Anthony Liguori
2011-08-08 13:41   ` Alexander Graf
2011-08-08 13:46     ` Anthony Liguori
2011-08-08 13:49     ` Avi Kivity
2011-08-08 13:51   ` Avi Kivity
2011-08-08 14:15     ` Anthony Liguori
2011-08-08 14:23       ` Avi Kivity
2011-08-08 14:33         ` Anthony Liguori
2011-08-08 14:39           ` Avi Kivity
2011-08-08 15:08             ` Anthony Liguori
2011-08-08 14:04   ` [Qemu-devel] [libvirt] " Daniel P. Berrange
2011-08-08 14:42     ` Avi Kivity
2011-08-08 14:46 ` [Qemu-devel] " Avi Kivity
2011-08-08 14:47   ` Avi Kivity
2011-08-08 14:56     ` Stefan Hajnoczi
2011-08-08 15:01       ` Avi Kivity
2011-08-08 15:10     ` Anthony Liguori [this message]
2011-08-08 15:15       ` Avi Kivity
2011-08-08 16:19         ` Anthony Liguori
2011-08-08 16:53           ` Avi Kivity
2011-08-08 16:55             ` Anthony Liguori
2011-08-10 15:07               ` Shribman, Aidan
2011-08-10 15:12                 ` Avi Kivity
2011-08-10 15:58                   ` Anthony Liguori
2011-08-10 16:08                     ` Avi Kivity
2011-08-10 16:23                       ` Anthony Liguori
2011-08-10 16:40                         ` Avi Kivity
2011-08-10 19:27                           ` Anthony Liguori
2011-08-11  8:03                             ` Shribman, Aidan
2011-08-11 13:00                               ` Anthony Liguori
2011-08-11  8:17                             ` Avi Kivity
2011-08-11  9:16                               ` [Qemu-devel] [libvirt] " Daniel P. Berrange
2011-08-11  9:20                                 ` Avi Kivity
2011-08-11 13:03                               ` [Qemu-devel] " Anthony Liguori
2011-08-11  9:24                             ` [Qemu-devel] [libvirt] " Daniel P. Berrange

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=4E3FFC7A.3090000@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=aidan.shribman@sap.com \
    --cc=avi@redhat.com \
    --cc=blauwirbel@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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).