qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Jason J. Herne" <jjherne@linux.vnet.ibm.com>
To: Eric Blake <eblake@redhat.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: Fri, 04 Sep 2015 11:09:46 -0400	[thread overview]
Message-ID: <55E9B43A.7070304@linux.vnet.ibm.com> (raw)
In-Reply-To: <55E6181D.3080709@redhat.com>

On 09/01/2015 05:26 PM, Eric Blake wrote:
> 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?
>

Not a clue :) I have no idea how things move from x- to sans x-.

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

The call to cpu_throttle_set will take care of the capping. Details
provided in previous reply :)
...
> We've missed 2.4; these lines need to say (Since 2.5).
...
>>   # Since: 2.4
...
> Would be nice to document the default (20).
...
> And again (10).  Also, same comment about needing 2.5.
>

I will fix all of these.

-- 
-- Jason J. Herne (jjherne@linux.vnet.ibm.com)

  reply	other threads:[~2015-09-04 15:10 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
2015-09-04 15:09     ` Jason J. Herne [this message]
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=55E9B43A.7070304@linux.vnet.ibm.com \
    --to=jjherne@linux.vnet.ibm.com \
    --cc=afaerber@suse.de \
    --cc=amit.shah@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=dgilbert@redhat.com \
    --cc=eblake@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 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).