From: Avi Kivity <avi@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Dor Laor <dlaor@redhat.com>,
qemu-devel Developers <qemu-devel@nongnu.org>,
libvirt-list@redhat.com, Blue Swirl <blauwirbel@gmail.com>,
"Shribman, Aidan" <aidan.shribman@sap.com>
Subject: Re: [Qemu-devel] [libvirt] [PATCH v4] XBZRLE delta for live migration of large memory apps
Date: Mon, 08 Aug 2011 17:42:05 +0300 [thread overview]
Message-ID: <4E3FF5BD.4080008@redhat.com> (raw)
In-Reply-To: <20110808140444.GB5699@redhat.com>
On 08/08/2011 05:04 PM, Daniel P. Berrange wrote:
> My main concern with all these scenarios where libvirt touches the
> actual data stream though is that we're introducing extra data copies
> into the migration path which potentially waste CPU cycles.
> If QEMU can directly XBZRLE encode data into the FD passed via 'fd:'
> then we minimize data copies. Whether this is a big enough benefit
> to offset the burden of having to maintain various compression code
> options in QEMU I can't answer.
>
It's counterproductive to force an unneeded data copy in order to
increase bandwidth.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-08-08 14:42 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 [this message]
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
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=4E3FF5BD.4080008@redhat.com \
--to=avi@redhat.com \
--cc=aidan.shribman@sap.com \
--cc=berrange@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=dlaor@redhat.com \
--cc=libvirt-list@redhat.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).