~hyman <hy...@git.sr.ht> wrote:
> From: Hyman Huang(黄勇) <yong.hu...@smartx.com>
>
> Introduce migration dirty-limit capability, which can
> be turned on before live migration and limit dirty
> page rate durty live migration.
>
> Introduce migrate_dirty_limit function to help check
> if dirty-limit capability enabled during live migration.
>
> Meanwhile, refactor vcpu_dirty_rate_stat_collect
> so that period can be configured instead of hardcoded.
>
> dirty-limit capability is kind of like auto-converge
> but using dirty limit instead of traditional cpu-throttle
> to throttle guest down. To enable this feature, turn on
> the dirty-limit capability before live migration using
> migrate-set-capabilities, and set the parameters
> "x-vcpu-dirty-limit-period", "vcpu-dirty-limit" suitably
> to speed up convergence.
>
> Signed-off-by: Hyman Huang(黄勇) <yong.hu...@smartx.com>
> Acked-by: Peter Xu <pet...@redhat.com>
Reviewed-by: Juan Quintela <quint...@redhat.com>
> return s->capabilities[MIGRATION_CAPABILITY_AUTO_CONVERGE];
> }
>
> +bool migrate_dirty_limit(void)
> +{
> + MigrationState *s = migrate_get_current();
> +
> + return s->capabilities[MIGRATION_CAPABILITY_DIRTY_LIMIT];
> +}
> +
Not sorted O:-)
I know, I know, no docs.
> + vcpu_calculate_dirtyrate(period,
> + &stat,
> + GLOBAL_DIRTY_LIMIT,
> + false);
spaces, tabs and/or editor failed you.
Will fix by hand.
Later, Juan.
