All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Ashijeet Acharya <ashijeetacharya@gmail.com>
Cc: lcapitulino@redhat.com, quintela@redhat.com,
	amit.shah@redhat.com, eblake@redhat.com, armbru@redhat.com,
	dgilbert@redhat.com, pbonzini@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Move max-bandwidth and downtime-limit into migrate_set_parameter for both hmp and qmp
Date: Mon, 5 Sep 2016 18:56:20 +0100	[thread overview]
Message-ID: <20160905175619.GO24656@redhat.com> (raw)
In-Reply-To: <1473097811-13519-1-git-send-email-ashijeetacharya@gmail.com>

On Mon, Sep 05, 2016 at 11:20:11PM +0530, Ashijeet Acharya wrote:
> Mark old-commands for speed and downtime as deprecated.
> Move max-bandwidth and downtime-limit into migrate-set-parameters for
> setting maximum migration speed and expected downtime limit parameters
> respectively.
> Change downtime units to milliseconds and update the query part in both
> hmp and qmp qemu control interfaces.
> 
> Signed-off-by: Ashijeet Acharya <ashijeetacharya@gmail.com>
> ---
>  hmp-commands.hx               |   8 +--
>  hmp.c                         |  29 +++++++++-
>  include/migration/migration.h |   1 -
>  migration/migration.c         | 122 +++++++++++++++++++++++++++++++-----------
>  qapi-schema.json              |  37 ++++++++++---
>  qmp-commands.hx               |  21 +++++---
>  6 files changed, 169 insertions(+), 49 deletions(-)
> 
> diff --git a/hmp-commands.hx b/hmp-commands.hx
> index 848efee..c7f1ef9 100644
> --- a/hmp-commands.hx
> +++ b/hmp-commands.hx
> @@ -980,16 +980,16 @@ ETEXI
>  
>      {
>          .name       = "migrate_set_downtime",
> -        .args_type  = "value:T",
> +        .args_type  = "value:i",
>          .params     = "value",
> -        .help       = "set maximum tolerated downtime (in seconds) for migrations",
> +        .help       = "set maximum tolerated downtime (in milliseconds) for migrations",
>          .mhandler.cmd = hmp_migrate_set_downtime,
>      },
>  
>  STEXI
> -@item migrate_set_downtime @var{second}
> +@item migrate_set_downtime @var{milliseconds}
>  @findex migrate_set_downtime
> -Set maximum tolerated downtime (in seconds) for migration.
> +Set maximum tolerated downtime (in milliseconds) for migration.
>  ETEXI

Sorry, you misunderstood - while we should use 'milliseconds' for
downtime in the 'migrate_set_parameters' command, we cannot
change the existing 'migrate_set_downtime' command. Changing that
would break compatibility with existing apps.


> diff --git a/qapi-schema.json b/qapi-schema.json
> index 5658723..66ed582 100644
> --- a/qapi-schema.json
> +++ b/qapi-schema.json
> @@ -637,12 +637,19 @@
>  #                hostname must be provided so that the server's x509
>  #                certificate identity can be validated. (Since 2.7)
>  #
> +# @max-bandwidth: to set maximum speed for migration. maximum speed in
> +#                 bytes. (Since 2.8)

s/bytes/bytes per second/  (and elsewhere in this patch)

> +#
> +# @downtime-limit: set maximum tolerated downtime for migration. maximum downtime
> +#                  in milliseconds (Since 2.8)
> +#

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

  reply	other threads:[~2016-09-05 17:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-05 17:50 [Qemu-devel] [PATCH] Move max-bandwidth and downtime-limit into migrate_set_parameter for both hmp and qmp Ashijeet Acharya
2016-09-05 17:56 ` Daniel P. Berrange [this message]
2016-09-05 18:07   ` Ashijeet Acharya
2016-09-06  6:29     ` Ashijeet Acharya

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=20160905175619.GO24656@redhat.com \
    --to=berrange@redhat.com \
    --cc=amit.shah@redhat.com \
    --cc=armbru@redhat.com \
    --cc=ashijeetacharya@gmail.com \
    --cc=dgilbert@redhat.com \
    --cc=eblake@redhat.com \
    --cc=lcapitulino@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.