From: huangy81@chinatelecom.cn
To: qemu-devel <qemu-devel@nongnu.org>
Cc: "Hyman Huang" <huangy81@chinatelecom.cn>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Juan Quintela" <quintela@redhat.com>
Subject: [PATCH v2] Introduce dirty ring live migration test for guestperf
Date: Wed, 16 Mar 2022 21:39:05 +0800 [thread overview]
Message-ID: <cover.1647437453.git.huangy81@chinatelecom.cn> (raw)
From: Hyman Huang(黄勇) <huangy81@chinatelecom.cn>
v2:
- rebase on master
- fix style problems and make qemu test passes
Ping
Please review. Thanks,
Regards
Yong
v1:
- original version sent by accident, send the right patch
Dirtylimit implementation has been reviewed in the past few months, if
things go well, it will be merged in the near future, which is the first
step to implement a new live migration feature. For more details refer to:
https://lore.kernel.org/qemu-devel/cover.1646247968.git.huangy81@chinatelecom.cn/
The second step is to implement the "dirtylimit" capability of live
migration basing on the implementation in first step, and the main
logic is almost done, refer to:
https://github.com/newfriday/qemu/commits/migration_dirtylimit_v1
Since "dirtylimit" capability of live migration is basing on dirty
ring, so if we want compare live migration used "dirtylimit" capability
with other capabilities such as "auto-converge" in performance, set
dirty ring size when start vm using guestperf tool is an convenient way.
So let's introduce dirty ring size for guestperf tool.
Hyman Huang (1):
tests/migration: Introduce dirty-ring-size option into guestperf
tests/migration/guestperf/engine.py | 6 +++++-
tests/migration/guestperf/hardware.py | 8 ++++++--
tests/migration/guestperf/shell.py | 7 ++++++-
3 files changed, 17 insertions(+), 4 deletions(-)
--
1.8.3.1
next reply other threads:[~2022-03-16 13:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 13:39 huangy81 [this message]
2022-03-16 13:39 ` [PATCH v2] tests/migration: Introduce dirty-ring-size option into guestperf huangy81
2022-03-23 14:06 ` Hyman Huang
2022-04-01 13:05 ` Hyman Huang
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=cover.1647437453.git.huangy81@chinatelecom.cn \
--to=huangy81@chinatelecom.cn \
--cc=berrange@redhat.com \
--cc=dgilbert@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.