[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH] introduce dirty ring size for guestperf tool
From: |
huangy81 |
Subject: |
[PATCH] introduce dirty ring size for guestperf tool |
Date: |
Thu, 3 Mar 2022 18:45:05 +0800 |
From: Hyman Huang(黄勇) <huangy81@chinatelecom.cn>
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:
cover.1646247968.git.huangy81@chinatelecom.cn/">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 | 6 +++++-
3 files changed, 16 insertions(+), 4 deletions(-)
--
1.8.3.1
- [PATCH] introduce dirty ring size for guestperf tool,
huangy81 <=