[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 1/8] qapi/migration: Introduce x-vcpu-dirty-limit-period para
From: |
Peter Xu |
Subject: |
Re: [PATCH 1/8] qapi/migration: Introduce x-vcpu-dirty-limit-period parameter |
Date: |
Wed, 17 Aug 2022 18:06:16 -0400 |
On Sat, Jul 23, 2022 at 03:49:13PM +0800, huangy81@chinatelecom.cn wrote:
> From: Hyman Huang(黄勇) <huangy81@chinatelecom.cn>
>
> Introduce "x-vcpu-dirty-limit-period" migration experimental
> parameter, which is used to make dirtyrate calculation period
> configurable.
>
> Signed-off-by: Hyman Huang(黄勇) <huangy81@chinatelecom.cn>
> ---
> migration/migration.c | 16 ++++++++++++++++
> monitor/hmp-cmds.c | 8 ++++++++
> qapi/migration.json | 31 ++++++++++++++++++++++++-------
> 3 files changed, 48 insertions(+), 7 deletions(-)
>
> diff --git a/migration/migration.c b/migration/migration.c
> index e03f698..7b19f85 100644
> --- a/migration/migration.c
> +++ b/migration/migration.c
> @@ -116,6 +116,8 @@
> #define DEFAULT_MIGRATE_ANNOUNCE_ROUNDS 5
> #define DEFAULT_MIGRATE_ANNOUNCE_STEP 100
>
> +#define DEFAULT_MIGRATE_VCPU_DIRTY_LIMIT_PERIOD 500 /* ms */
Why 500 but not DIRTYLIMIT_CALC_TIME_MS?
Is it intended to make this parameter experimental, but the other one not?
Thanks,
--
Peter Xu
- Re: [PATCH 1/8] qapi/migration: Introduce x-vcpu-dirty-limit-period parameter,
Peter Xu <=