From: Peter Lieven <lieven-lists@dlhnet.de>
To: Chegu Vinod <chegu_vinod@hp.com>
Cc: quintela@redhat.com, qemu-devel@nongnu.org, owasserm@redhat.com,
anthony@codemonkey.ws, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH v8 0/3] Throttle-down guest to help with live migration convergence
Date: Thu, 18 Jul 2013 08:24:35 +0200 [thread overview]
Message-ID: <51E78A23.80605@dlhnet.de> (raw)
In-Reply-To: <1372067382-141082-1-git-send-email-chegu_vinod@hp.com>
Hi all,
is it possible that not v8 of this patch got merged?
Without checking line-by-line I see at least that this here
+# @auto-converge: If enabled, QEMU will automatically throttle down the guest
+# to speed up convergence of RAM migration. (since 1.6)
+#
is missing in qapi-schema.json.
BR,
Peter
On 24.06.2013 11:49, 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.
>
> If a user chooses to force convergence of their migration via a new
> migration capability "auto-converge" then this change will auto-detect
> lack of convergence scenario and trigger a slow down of the workload
> by explicitly disallowing the VCPUs from spending much time in the VM
> context.
>
> The migration thread tries to catchup and this eventually leads
> to convergence in some "deterministic" amount of time. Yes it does
> impact the performance of all the VCPUs but in my observation that
> lasts only for a short duration of time. i.e. end up entering
> stage 3 (downtime phase) soon after that. No external trigger is
> required.
>
> Thanks to Juan and Paolo for their useful suggestions.
>
> ---
> Changes from v7:
> - added a missing else to patch 3/3.
>
> Changes from v6:
> - incorporated feedback from Paolo.
> - rebased to latest qemu.git and removing RFC
>
> Changes from v5:
> - incorporated feedback from Paolo & Igor.
> - rebased to latest qemu.git
>
> Changes from v4:
> - incorporated feedback from Paolo.
> - split into 3 patches.
>
> Changes from v3:
> - incorporated feedback from Paolo and Eric
> - rebased to latest qemu.git
>
> 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
>
> Changes from v1:
> - rebased to latest qemu.git
> - added auto-converge capability(default off) - suggested by Anthony Liguori &
> Eric Blake.
>
> Signed-off-by: Chegu Vinod <chegu_vinod@hp.com>
> ---
>
> Chegu Vinod (3):
> Introduce async_run_on_cpu()
> Add 'auto-converge' migration capability
> Force auto-convegence of live migration
>
> arch_init.c | 85 +++++++++++++++++++++++++++++++++++++++++
> cpus.c | 29 ++++++++++++++
> include/migration/migration.h | 2 +
> include/qemu-common.h | 1 +
> include/qom/cpu.h | 10 +++++
> migration.c | 9 ++++
> qapi-schema.json | 5 ++-
> 7 files changed, 140 insertions(+), 1 deletions(-)
>
>
next prev parent reply other threads:[~2013-07-18 6:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 9:49 [Qemu-devel] [PATCH v8 0/3] Throttle-down guest to help with live migration convergence Chegu Vinod
2013-06-24 9:49 ` [Qemu-devel] [PATCH v8 1/3] Introduce async_run_on_cpu() Chegu Vinod
2013-07-12 11:54 ` Juan Quintela
2013-07-13 9:15 ` Orit Wasserman
2013-06-24 9:49 ` [Qemu-devel] [PATCH v8 2/3] Add 'auto-converge' migration capability Chegu Vinod
2013-07-12 11:56 ` Juan Quintela
2013-07-13 9:17 ` Orit Wasserman
2013-07-18 6:24 ` Peter Lieven [this message]
2013-07-18 17:42 ` [Qemu-devel] [PATCH v8 0/3] Throttle-down guest to help with live migration convergence Vinod, Chegu
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=51E78A23.80605@dlhnet.de \
--to=lieven-lists@dlhnet.de \
--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).