From: Eric Blake <eblake@redhat.com>
To: "Jason J. Herne" <jjherne@linux.vnet.ibm.com>,
afaerber@suse.de, amit.shah@redhat.com, dgilbert@redhat.com,
borntraeger@de.ibm.com, quintela@redhat.com,
qemu-devel@nongnu.org, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH v5 2/5] migration: Parameters for auto-converge cpu throttling
Date: Tue, 1 Sep 2015 15:26:53 -0600 [thread overview]
Message-ID: <55E6181D.3080709@redhat.com> (raw)
In-Reply-To: <1441118763-17510-3-git-send-email-jjherne@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 3476 bytes --]
On 09/01/2015 08:46 AM, Jason J. Herne wrote:
> Add migration parameters to allow the user to adjust the parameters
> that control cpu throttling when auto-converge is in effect. The added
> parameters are as follows:
>
> x-cpu-throttle-initial : Initial percantage of time guest cpus are throttled
> when migration auto-converge is activated.
>
> x-cpu-throttle-increment: throttle percantage increase each time
> auto-converge detects that migration is not making progress.
Marked experimental; do we think it will be promoted to stable before
2.5 is released?
What happens if I set throttle-initial to 50 and throttle-increment to
50? The previous patch required throttle percentage to be between 1 and
99 inclusive; does that mean I cap out at 99 instead of an invalid
throttle of 100?
>
> Signed-off-by: Jason J. Herne <jjherne@linux.vnet.ibm.com>
> Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> ---
> hmp.c | 16 ++++++++++++++++
> migration/migration.c | 46 +++++++++++++++++++++++++++++++++++++++++++++-
> qapi-schema.json | 33 ++++++++++++++++++++++++++++++---
> 3 files changed, 91 insertions(+), 4 deletions(-)
>
> +++ b/qapi-schema.json
> @@ -587,10 +587,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.
> +# (Since 2.4)
> +#
> +# @x-cpu-throttle-increment: throttle percentage increase each time
> +# auto-converge detects that migration is not making
> +# progress. (Since 2.4)
We've missed 2.4; these lines need to say (Since 2.5).
> # Since: 2.4
> ##
> { 'enum': 'MigrationParameter',
> - 'data': ['compress-level', 'compress-threads', 'decompress-threads'] }
> + 'data': ['compress-level', 'compress-threads', 'decompress-threads',
> + 'x-cpu-throttle-initial', 'x-cpu-throttle-increment'] }
>
> #
> # @migrate-set-parameters
> @@ -603,12 +611,22 @@
> #
> # @decompress-threads: decompression thread count
> #
> +# @x-cpu-throttle-initial: Initial percentage of time guest cpus are throttled
> +# when migration auto-converge is activated.
> +# (Since 2.4)
Would be nice to document the default (20).
> +#
> +# @x-cpu-throttle-increment: throttle percentage increase each time
> +# auto-converge detects that migration is not making
> +# progress. (Since 2.4)
And again (10). Also, same comment about needing 2.5.
> @@ -618,13 +636,22 @@
> # @compress-threads: compression thread count
> #
> # @decompress-threads: decompression thread count
> +# @x-cpu-throttle-initial: Initial percentage of time guest cpus are throttled
> +# when migration auto-converge is activated.
> +# (Since 2.4)
> +#
> +# @x-cpu-throttle-increment: throttle percentage increase each time
> +# auto-converge detects that migration is not making
> +# progress. (Since 2.4)
2.5.
--
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 --]
next prev parent reply other threads:[~2015-09-01 21:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 14:45 [Qemu-devel] [PATCH v5 0/5] migration: Dynamic cpu throttling for auto-converge Jason J. Herne
2015-09-01 14:45 ` [Qemu-devel] [PATCH v5 1/5] cpu: Provide vcpu throttling interface Jason J. Herne
2015-09-01 21:23 ` Eric Blake
2015-09-04 15:17 ` Jason J. Herne
2015-09-01 14:46 ` [Qemu-devel] [PATCH v5 2/5] migration: Parameters for auto-converge cpu throttling Jason J. Herne
2015-09-01 21:26 ` Eric Blake [this message]
2015-09-04 15:09 ` Jason J. Herne
2015-09-01 14:46 ` [Qemu-devel] [PATCH v5 3/5] migration: Dynamic cpu throttling for auto-converge Jason J. Herne
2015-09-01 21:30 ` Eric Blake
2015-09-04 14:54 ` Jason J. Herne
2015-09-01 14:46 ` [Qemu-devel] [PATCH v5 4/5] qmp/hmp: Add throttle ratio to query-migrate and info migrate Jason J. Herne
2015-09-01 21:31 ` Eric Blake
2015-09-01 14:46 ` [Qemu-devel] [PATCH v5 5/5] migration: Disambiguate MAX_THROTTLE Jason J. Herne
2015-09-01 21:32 ` Eric Blake
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=55E6181D.3080709@redhat.com \
--to=eblake@redhat.com \
--cc=afaerber@suse.de \
--cc=amit.shah@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=dgilbert@redhat.com \
--cc=jjherne@linux.vnet.ibm.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.