From: Li Qiang <liq3ea@gmail.com>
To: pbonzini@redhat.com, crosthwaite.peter@gmail.com,
rth@twiddle.net, quintela@redhat.com, dgilbert@redhat.com,
eblake@redhat.com, armbru@redhat.com
Cc: liqiang02@corp.netease.com, hzliuyingdong@corp.netease.com,
qemu-devel@nongnu.org, Li Qiang <liq3ea@gmail.com>
Subject: [Qemu-devel] [PATCH 0/3] Add a new migrate_set_max_cpu_throttle qmp command
Date: Tue, 31 Jul 2018 01:35:21 -0700 [thread overview]
Message-ID: <1533026124-6740-1-git-send-email-liq3ea@gmail.com> (raw)
Currently, the default maximum CPU throttle for migration is
99(CPU_THROTTLE_PCT_MAX). This is too big and can make a remarkable
performance effect for the guest. We see a lot of packets latency
exceed 500ms when the CPU_THROTTLE_PCT_MAX reached. This patch set
adds a new qmp command to limit the CPU throttle.
Li Qiang (3):
migrate: replace the cpu throttle percentage max with a variable
migration: Add qmp command for migrate_set_max_cpu_throttle
hmp: add hmp for migrate_set_max_cpu_throttle
cpus.c | 9 ++++++++-
hmp-commands.hx | 14 ++++++++++++++
hmp.c | 6 ++++++
hmp.h | 1 +
include/qom/cpu.h | 8 ++++++++
migration/migration.c | 10 ++++++++++
qapi/migration.json | 13 +++++++++++++
7 files changed, 60 insertions(+), 1 deletion(-)
--
2.11.0
next reply other threads:[~2018-07-31 8:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 8:35 Li Qiang [this message]
2018-07-31 8:35 ` [Qemu-devel] [PATCH 1/3] migrate: replace the cpu throttle percentage max with a variable Li Qiang
2018-07-31 8:35 ` [Qemu-devel] [PATCH 2/3] migration: Add qmp command for migrate_set_max_cpu_throttle Li Qiang
2018-07-31 11:29 ` Dr. David Alan Gilbert
2018-07-31 12:22 ` Eric Blake
2018-07-31 14:48 ` Juan Quintela
2018-07-31 15:38 ` Dr. David Alan Gilbert
2018-07-31 15:50 ` Daniel P. Berrangé
2018-08-01 1:14 ` Li Qiang
2018-08-01 8:01 ` Juan Quintela
2018-07-31 8:35 ` [Qemu-devel] [PATCH 3/3] hmp: add hmp " Li Qiang
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=1533026124-6740-1-git-send-email-liq3ea@gmail.com \
--to=liq3ea@gmail.com \
--cc=armbru@redhat.com \
--cc=crosthwaite.peter@gmail.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=hzliuyingdong@corp.netease.com \
--cc=liqiang02@corp.netease.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=rth@twiddle.net \
/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).