From: Eric Blake <eblake@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: owasserm@redhat.com, Chegu Vinod <chegu_vinod@hp.com>,
qemu-devel@nongnu.org, anthony@codemonkey.ws,
quintela@redhat.com
Subject: Re: [Qemu-devel] [RFC PATCH v5 2/3] Add 'auto-converge' migration capability
Date: Fri, 10 May 2013 08:26:41 -0600 [thread overview]
Message-ID: <518D03A1.20303@redhat.com> (raw)
In-Reply-To: <518CA508.4090100@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 763 bytes --]
On 05/10/2013 01:43 AM, Paolo Bonzini wrote:
>> +++ b/qapi-schema.json
>> @@ -602,10 +602,13 @@
>> # This feature allows us to minimize migration traffic for certain work
>> # loads, by sending compressed difference of the pages
>> #
>> +# @auto-converge: Migration supports automatic throttling down of guest
>> +# to force convergence. (since 1.6)
>
> If enabled, QEMU will automatically throttle down the guest to speed up
> convergence of RAM migration.
Ooh, I do like Paolo's wording better than mine. But either one is
reasonable, so feel free to add:
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
next prev parent reply other threads:[~2013-05-10 14:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 19:43 [Qemu-devel] [RFC PATCH v5 0/3] Throttle-down guest to help with live migration convergence Chegu Vinod
2013-05-09 19:43 ` [Qemu-devel] [RFC PATCH v5 1/3] Introduce async_run_on_cpu() Chegu Vinod
2013-05-10 7:43 ` Paolo Bonzini
2013-05-09 19:43 ` [Qemu-devel] [RFC PATCH v5 2/3] Add 'auto-converge' migration capability Chegu Vinod
2013-05-10 7:43 ` Paolo Bonzini
2013-05-10 14:26 ` Eric Blake [this message]
2013-05-09 19:43 ` [Qemu-devel] [RFC PATCH v5 3/3] Force auto-convegence of live migration Chegu Vinod
2013-05-09 20:05 ` Igor Mammedov
2013-05-09 22:26 ` Chegu Vinod
2013-05-09 20:24 ` Igor Mammedov
2013-05-09 23:00 ` Chegu Vinod
2013-05-10 7:47 ` Paolo Bonzini
2013-05-10 7:41 ` Paolo Bonzini
2013-05-10 13:07 ` Anthony Liguori
2013-05-10 14:14 ` Chegu Vinod
2013-05-10 15:11 ` Anthony Liguori
2013-05-12 17:19 ` Paolo Bonzini
2013-05-13 12:18 ` Anthony Liguori
2013-05-10 14:17 ` Daniel P. Berrange
2013-05-10 15:08 ` Anthony Liguori
2013-05-13 12:33 ` 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=518D03A1.20303@redhat.com \
--to=eblake@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=chegu_vinod@hp.com \
--cc=owasserm@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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).