From: Orit Wasserman <owasserm@redhat.com>
To: Chegu Vinod <chegu_vinod@hp.com>
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org,
anthony@codemonkey.ws, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH v8 2/3] Add 'auto-converge' migration capability
Date: Sat, 13 Jul 2013 12:17:42 +0300 [thread overview]
Message-ID: <51E11B36.7060606@redhat.com> (raw)
In-Reply-To: <1372067382-141082-3-git-send-email-chegu_vinod@hp.com>
On 06/24/2013 12:49 PM, Chegu Vinod wrote:
> The auto-converge migration capability allows the user to specify if they
> choose live migration seqeunce to automatically detect and force convergence.
>
> Signed-off-by: Chegu Vinod <chegu_vinod@hp.com>
> Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
> Reviewed-by: Eric Blake <eblake@redhat.com>
> ---
> include/migration/migration.h | 2 ++
> migration.c | 9 +++++++++
> qapi-schema.json | 5 ++++-
> 3 files changed, 15 insertions(+), 1 deletions(-)
>
> diff --git a/include/migration/migration.h b/include/migration/migration.h
> index e2acec6..ace91b0 100644
> --- a/include/migration/migration.h
> +++ b/include/migration/migration.h
> @@ -127,4 +127,6 @@ int migrate_use_xbzrle(void);
> int64_t migrate_xbzrle_cache_size(void);
>
> int64_t xbzrle_cache_resize(int64_t new_size);
> +
> +bool migrate_auto_converge(void);
> #endif
> diff --git a/migration.c b/migration.c
> index 058f9e6..d0759c1 100644
> --- a/migration.c
> +++ b/migration.c
> @@ -473,6 +473,15 @@ void qmp_migrate_set_downtime(double value, Error **errp)
> max_downtime = (uint64_t)value;
> }
>
> +bool migrate_auto_converge(void)
> +{
> + MigrationState *s;
> +
> + s = migrate_get_current();
> +
> + return s->enabled_capabilities[MIGRATION_CAPABILITY_AUTO_CONVERGE];
> +}
> +
> int migrate_use_xbzrle(void)
> {
> MigrationState *s;
> diff --git a/qapi-schema.json b/qapi-schema.json
> index a80ee40..c019fec 100644
> --- a/qapi-schema.json
> +++ b/qapi-schema.json
> @@ -605,10 +605,13 @@
> # This feature allows us to minimize migration traffic for certain work
> # loads, by sending compressed difference of the pages
> #
> +# @auto-converge: If enabled, QEMU will automatically throttle down the guest
> +# to speed up convergence of RAM migration. (since 1.6)
> +#
> # Since: 1.2
> ##
> { 'enum': 'MigrationCapability',
> - 'data': ['xbzrle'] }
> + 'data': ['xbzrle', 'auto-converge'] }
>
> ##
> # @MigrationCapabilityStatus
>
Reviewed-by: Orit Wasserman <owasserm@redhat.com>
next prev parent reply other threads:[~2013-07-13 9:16 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 [this message]
2013-07-18 6:24 ` [Qemu-devel] [PATCH v8 0/3] Throttle-down guest to help with live migration convergence Peter Lieven
2013-07-18 17:42 ` 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=51E11B36.7060606@redhat.com \
--to=owasserm@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=chegu_vinod@hp.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).