qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: quintela@redhat.com, QEMU Developer <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Migration ToDo list (a.k.a. Rant)
Date: Wed, 4 May 2016 07:38:31 -0600	[thread overview]
Message-ID: <5729FB57.60904@redhat.com> (raw)
In-Reply-To: <87oa8mf4sj.fsf@emacs.mitica>

[-- Attachment #1: Type: text/plain, Size: 2207 bytes --]

On 05/04/2016 05:20 AM, Juan Quintela wrote:
> - migration capabilities and parameters
>   this is a mess.  Not, is worse than that.  I don't know who is to
>   blame here, but something needs to be done:
> 
>      void qmp_migrate_set_parameters(bool has_compress_level,
>                                 int64_t compress_level,
>                                 bool has_compress_threads,
>                                 int64_t compress_threads,
>                                 bool has_decompress_threads,
>                                 int64_t decompress_threads,
>                                 bool has_x_cpu_throttle_initial,
>                                 int64_t x_cpu_throttle_initial,
>                                 bool has_x_cpu_throttle_increment,
>                                 int64_t x_cpu_throttle_increment,
>                                 bool has_multifd_threads,
>                                 int64_t multifd_threads,
>                                 Error **errp)

I've got a QAPI patch in the pipeline that makes this MUCH simpler, by
boxing everything through a single MigrationParameter* pointer rather
than an exploded list of parameters.


>    migrate_set_capability
>       Minor nickpit, if it only allow booleans, "migrate_set_capability x-multifd",
>       should be an equivalent of "migrate_set_capability x-multifd on"

That's HMP - you can make HMP do whatever you want without breaking
back-compat.

> 
>    migrate_set_cache_size
>    migrate_set_downtime
>    migrate_set_speed
>       This three should be claimed obsolete, deprecated, whatever, and
>       make it on top of next one

Again, HMP can make this change easy, even if it has to call out to
different QMP under the hood.

> 
>    migrate_set_parameter
> 
>    Now to read the migration information:
> 
>      migrate_capabilities
>        good
>      migrate_parameters
>        good

Why we need two commands is beyond me - one command that lists
everything (capabilities AND parameters) should be sufficient.


-- 
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: 604 bytes --]

  parent reply	other threads:[~2016-05-04 13:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-04 11:20 [Qemu-devel] Migration ToDo list (a.k.a. Rant) Juan Quintela
2016-05-04 12:47 ` Dr. David Alan Gilbert
2016-05-04 16:35   ` Greg Kurz
2016-05-04 13:08 ` Denis V. Lunev
2016-05-04 13:38 ` Eric Blake [this message]
2016-05-04 14:30   ` Juan Quintela
2016-06-16  9:05     ` Markus Armbruster
2016-05-05  6:19 ` Hailiang Zhang
2016-05-05  8:01 ` Li, Liang Z

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=5729FB57.60904@redhat.com \
    --to=eblake@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).