From: Eric Blake <eblake@redhat.com>
To: Chegu Vinod <chegu_vinod@hp.com>
Cc: owasserm@redhat.com, pbonzini@redhat.com, qemu-devel@nongnu.org,
anthony@codemonkey.ws, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3] Throttle-down guest when live migration does not converge.
Date: Wed, 01 May 2013 06:38:24 -0600 [thread overview]
Message-ID: <51810CC0.2080407@redhat.com> (raw)
In-Reply-To: <1367410972-22972-1-git-send-email-chegu_vinod@hp.com>
[-- Attachment #1: Type: text/plain, Size: 1874 bytes --]
On 05/01/2013 06:22 AM, Chegu Vinod wrote:
> Busy enterprise workloads hosted on large sized VM's tend to dirty
> memory faster than the transfer rate achieved via live guest migration.
> Despite some good recent improvements (& using dedicated 10Gig NICs
> between hosts) the live migration does NOT converge.
>
> ---
>
> Changes from v2:
> - incorporated feedback from Orit, Juan and Eric
> - stop the throttling thread at the start of stage 3
> - rebased to latest qemu.git
>
> +++ b/qapi-schema.json
> @@ -600,9 +600,14 @@
> # loads, by sending compressed difference of the pages
> #
> # Since: 1.2
> +#
> +# @auto-converge: Migration supports automatic throttling down of guest
> +# to force convergence. Disabled by default.
> +#
> +# Since: 1.6
> ##
I've already argued that ALL new migration capabilities should be
disabled by default (see the thread on 'x-rdma-pin-all', which will be a
merge conflict if it gets applied before your patch). So I don't think
that last sentence adds anything, and can be dropped.
I think this works, although it's the first instance of having two
top-level Since: tags on a single JSON entity. I was envisioning:
@xbzrle: yadda... pages
@auto-convert: Migration supports... convergence (since 1.6)
Since: 1.2
to match the conventions elsewhere that the overall JSON entity (the
enum MigrationCapability) exists since 1.2, but the addition of
auto-convert happened in 1.6.
However, as nothing parses the .json file to turn it into formal docs
(yet), I'm not going to insist on a respin if this is the only problem
with your patch. I'm not comfortable enough with my skills in reviewing
the rest of the patch, or I'd offer a reviewed-by.
--
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-01 12:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 12:22 [Qemu-devel] [PATCH v3] Throttle-down guest when live migration does not converge Chegu Vinod
2013-05-01 12:38 ` Eric Blake [this message]
2013-05-01 12:50 ` Chegu Vinod
2013-05-01 15:40 ` Paolo Bonzini
2013-05-01 16:34 ` Chegu Vinod
2013-05-01 17:03 ` Paolo Bonzini
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=51810CC0.2080407@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 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.