qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: "Jason J. Herne" <jjherne@linux.vnet.ibm.com>,
	amit.shah@redhat.com, dgilbert@redhat.com, quintela@redhat.com,
	qemu-devel@nongnu.org, jdenemar@redhat.com
Subject: Re: [Qemu-devel] [PATCH] migration: Promote improved autoconverge commands out of experimental state
Date: Thu, 21 Apr 2016 09:47:21 -0600	[thread overview]
Message-ID: <5718F609.20802@redhat.com> (raw)
In-Reply-To: <1461253141-19722-1-git-send-email-jjherne@linux.vnet.ibm.com>

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

On 04/21/2016 09:39 AM, Jason J. Herne wrote:
> The new autoconverge throttling commands have been tested for a release now. It
> is time to move them out of the experimental state.
> 
> Signed-off-by: Jason J. Herne <jjherne@linux.vnet.ibm.com>
> ---

> +++ b/qapi-schema.json
> @@ -480,9 +480,9 @@
>  #        may be expensive, but do not actually occur during the iterative
>  #        migration rounds themselves. (since 1.6)
>  #
> -# @x-cpu-throttle-percentage: #optional percentage of time guest cpus are being
> -#       throttled during auto-converge. This is only present when auto-converge
> -#       has started throttling guest cpus. (Since 2.5)
> +# @cpu-throttle-percentage: #optional percentage of time guest cpus are being
> +#        throttled during auto-converge. This is only present when auto-converge
> +#        has started throttling guest cpus. (Since 2.5)

s/2.5/2.7/ - while the grunt work has been around since 2.5, the actual
'cpu-throttle-percentage' option is new to 2.7.  Listing the time of
promotion matches what we have done elsewhere when promoting things to
stable.

> @@ -605,18 +605,18 @@
>  #          compression, so set the decompress-threads to the number about 1/4
>  #          of compress-threads is adequate.
>  #
> -# @x-cpu-throttle-initial: Initial percentage of time guest cpus are throttled
> -#                          when migration auto-converge is activated. The
> -#                          default value is 20. (Since 2.5)
> +# @cpu-throttle-initial: Initial percentage of time guest cpus are throttled
> +#                        when migration auto-converge is activated. The
> +#                        default value is 20. (Since 2.5)
>  #
> -# @x-cpu-throttle-increment: throttle percentage increase each time
> -#                            auto-converge detects that migration is not making
> -#                            progress. The default value is 10. (Since 2.5)
> +# @cpu-throttle-increment: throttle percentage increase each time
> +#                          auto-converge detects that migration is not making
> +#                          progress. The default value is 10. (Since 2.5)


Two more instances.

> @@ -629,21 +629,21 @@
>  #
>  # @decompress-threads: decompression thread count
>  #
> -# @x-cpu-throttle-initial: Initial percentage of time guest cpus are throttled
> -#                          when migration auto-converge is activated. The
> -#                          default value is 20. (Since 2.5)
> +# @cpu-throttle-initial: Initial percentage of time guest cpus are throttled
> +#                        when migration auto-converge is activated. The
> +#                        default value is 20. (Since 2.5)
>  #
> -# @x-cpu-throttle-increment: throttle percentage increase each time
> -#                            auto-converge detects that migration is not making
> -#                            progress. The default value is 10. (Since 2.5)
> +# @cpu-throttle-increment: throttle percentage increase each time
> +#                          auto-converge detects that migration is not making
> +#                          progress. The default value is 10. (Since 2.5)

And again.

> @@ -654,13 +654,13 @@
>  #
>  # @decompress-threads: decompression thread count
>  #
> -# @x-cpu-throttle-initial: Initial percentage of time guest cpus are throttled
> -#                          when migration auto-converge is activated. The
> -#                          default value is 20. (Since 2.5)
> +# @cpu-throttle-initial: Initial percentage of time guest cpus are throttled
> +#                        when migration auto-converge is activated. The
> +#                        default value is 20. (Since 2.5)
>  #
> -# @x-cpu-throttle-increment: throttle percentage increase each time
> -#                            auto-converge detects that migration is not making
> -#                            progress. The default value is 10. (Since 2.5)
> +# @cpu-throttle-increment: throttle percentage increase each time
> +#                          auto-converge detects that migration is not making
> +#                          progress. The default value is 10. (Since 2.5)

and again

-- 
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 --]

      reply	other threads:[~2016-04-21 15:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-21 15:39 [Qemu-devel] [PATCH] migration: Promote improved autoconverge commands out of experimental state Jason J. Herne
2016-04-21 15:47 ` Eric Blake [this message]

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=5718F609.20802@redhat.com \
    --to=eblake@redhat.com \
    --cc=amit.shah@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=jdenemar@redhat.com \
    --cc=jjherne@linux.vnet.ibm.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).