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
Subject: Re: [Qemu-devel] [PATCH v2 2/3] migration: Dynamic cpu throttling for auto-converge
Date: Tue, 02 Jun 2015 14:08:05 -0600 [thread overview]
Message-ID: <556E0D25.10302@redhat.com> (raw)
In-Reply-To: <1433267209-9882-3-git-send-email-jjherne@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1443 bytes --]
On 06/02/2015 11:46 AM, Jason J. Herne wrote:
> Remove traditional auto-converge static 30ms throttling code and replace it
> with a dynamic throttling algorithm.
>
> Additionally, be more aggressive when deciding when to start throttling.
> Previously we waited until four unproductive memory passes. Now we begin
> throttling after only two unproductive memory passes. Four seemed quite
> arbitrary and only waiting for two passes allows us to complete the migration
> faster.
>
> Signed-off-by: Jason J. Herne <jjherne@linux.vnet.ibm.com>
> Reviewed-by: Matthew Rosato <mjrosato@linux.vnet.ibm.com>
> ---
> arch_init.c | 95 +++++++++++++++++----------------------------------
> migration/migration.c | 9 +++++
> 2 files changed, 41 insertions(+), 63 deletions(-)
>
> +static void mig_throttle_guest_down(void)
> +{
> + CPUState *cpu;
> +
> + CPU_FOREACH(cpu) {
> + /* We have not started throttling yet. Lets start it.*/
s/Lets/Let's/
s|it.*/|it. */|
> + if (!cpu_throttle_active(cpu)) {
> + cpu_throttle_start(cpu, 0.2);
> + }
> +
> + /* Throttling is already in place. Just increase the throttling rate */
> + else {
Unusual layout. More typical would be:
if (...) {
...
} else {
/* comment */
...
}
--
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-06-02 20:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 17:46 [Qemu-devel] [PATCH v2 0/3] migration: Dynamic cpu throttling for auto-converge Jason J. Herne
2015-06-02 17:46 ` [Qemu-devel] [PATCH v2 1/3] cpu: Provide vcpu throttling interface Jason J. Herne
2015-06-03 7:56 ` Juan Quintela
2015-06-03 18:02 ` Jason J. Herne
2015-06-03 18:03 ` Dr. David Alan Gilbert
2015-06-03 18:11 ` Jason J. Herne
2015-06-08 19:07 ` Jason J. Herne
2015-06-09 8:06 ` Dr. David Alan Gilbert
2015-06-09 15:14 ` Jason J. Herne
2015-06-10 8:45 ` Dr. David Alan Gilbert
2015-06-10 12:03 ` Jason J. Herne
2015-06-11 6:38 ` Markus Armbruster
2015-06-02 17:46 ` [Qemu-devel] [PATCH v2 2/3] migration: Dynamic cpu throttling for auto-converge Jason J. Herne
2015-06-02 20:08 ` Eric Blake [this message]
2015-06-02 17:46 ` [Qemu-devel] [PATCH v2 3/3] qmp/hmp: Add throttle ratio to query-migrate and info migrate Jason J. Herne
2015-06-02 20:11 ` Eric Blake
2015-06-03 17:45 ` Jason J. Herne
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=556E0D25.10302@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=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).