From: Markus Armbruster <armbru@redhat.com>
To: huangy81@chinatelecom.cn
Cc: qemu-devel <qemu-devel@nongnu.org>, Peter Xu <peterx@redhat.com>,
Juan Quintela <quintela@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Eric Blake <eblake@redhat.com>, Thomas Huth <thuth@redhat.com>,
Laurent Vivier <lvivier@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>
Subject: Re: [PATCH v1 2/8] qapi/migration: Introduce x-vcpu-dirty-limit parameters
Date: Fri, 02 Sep 2022 10:03:40 +0200 [thread overview]
Message-ID: <875yi6xkwz.fsf@pond.sub.org> (raw)
In-Reply-To: <58009ed32bc30ce40228b191fdd9cacc259ac859.1662052189.git.huangy81@chinatelecom.cn> (huangy's message of "Fri, 2 Sep 2022 01:22:30 +0800")
huangy81@chinatelecom.cn writes:
> From: Hyman Huang(黄勇) <huangy81@chinatelecom.cn>
>
> Introduce "x-vcpu-dirty-limit" migration parameter used
> to limit dirty page rate during live migration.
>
> "x-vcpu-dirty-limit" and "x-vcpu-dirty-limit-period" are
> two dirty-limit-related migration parameters, which can
> be set before and during live migration by qmp
> migrate-set-parameters.
>
> This two parameters are used to help implement the dirty
> page rate limit algo of migration.
>
> Signed-off-by: Hyman Huang(黄勇) <huangy81@chinatelecom.cn>
[...]
> diff --git a/qapi/migration.json b/qapi/migration.json
> index 332c087..8554d33 100644
> --- a/qapi/migration.json
> +++ b/qapi/migration.json
> @@ -779,6 +779,9 @@
> # @x-vcpu-dirty-limit-period: Periodic time (ms) of dirty limit during live migration.
> # Defaults to 500ms. (Since 7.1)
> #
> +# @x-vcpu-dirty-limit: Dirtyrate limit (MB/s) during live migration.
> +# Defaults to 1. (Since 7.1)
> +#
> # Features:
> # @unstable: Member @x-checkpoint-delay and @x-vcpu-dirty-limit-period
> # are experimental.
> @@ -801,7 +804,8 @@
> 'max-cpu-throttle', 'multifd-compression',
> 'multifd-zlib-level', 'multifd-zstd-level',
> 'block-bitmap-mapping',
> - { 'name': 'x-vcpu-dirty-limit-period', 'features': ['unstable'] } ] }
> + { 'name': 'x-vcpu-dirty-limit-period', 'features': ['unstable'] },
> + 'x-vcpu-dirty-limit'] }
Shouldn't 'x-vcpu-dirty-limit-period' have feature 'unstable', too?
Same below.
>
> ##
> # @MigrateSetParameters:
> @@ -949,6 +953,9 @@
> # @x-vcpu-dirty-limit-period: Periodic time (ms) of dirty limit during live migration.
> # Defaults to 500ms. (Since 7.1)
> #
> +# @x-vcpu-dirty-limit: Dirtyrate limit (MB/s) during live migration.
> +# Defaults to 1. (Since 7.1)
> +#
> # Features:
> # @unstable: Member @x-checkpoint-delay and @x-vcpu-dirty-limit-period
> # are experimental.
> @@ -987,7 +994,8 @@
> '*multifd-zstd-level': 'uint8',
> '*block-bitmap-mapping': [ 'BitmapMigrationNodeAlias' ],
> '*x-vcpu-dirty-limit-period': { 'type': 'uint64',
> - 'features': [ 'unstable' ] } } }
> + 'features': [ 'unstable' ] },
> + '*x-vcpu-dirty-limit': 'uint64'} }
>
> ##
> # @migrate-set-parameters:
> @@ -1155,6 +1163,9 @@
> # @x-vcpu-dirty-limit-period: Periodic time (ms) of dirty limit during live migration.
> # Defaults to 500ms. (Since 7.1)
> #
> +# @x-vcpu-dirty-limit: Dirtyrate limit (MB/s) during live migration.
> +# Defaults to 1. (Since 7.1)
> +#
> # Features:
> # @unstable: Member @x-checkpoint-delay and @x-vcpu-dirty-limit-period
> # are experimental.
> @@ -1191,7 +1202,8 @@
> '*multifd-zstd-level': 'uint8',
> '*block-bitmap-mapping': [ 'BitmapMigrationNodeAlias' ],
> '*x-vcpu-dirty-limit-period': { 'type': 'uint64',
> - 'features': [ 'unstable' ] } } }
> + 'features': [ 'unstable' ] },
> + '*x-vcpu-dirty-limit': 'uint64'} }
>
> ##
> # @query-migrate-parameters:
next prev parent reply other threads:[~2022-09-02 8:23 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 17:22 [PATCH v1 0/8] migration: introduce dirtylimit capability huangy81
2022-09-01 17:22 ` [PATCH v1 1/8] qapi/migration: Introduce x-vcpu-dirty-limit-period parameter huangy81
2022-09-02 8:02 ` Markus Armbruster
2022-09-01 17:22 ` [PATCH v1 2/8] qapi/migration: Introduce x-vcpu-dirty-limit parameters huangy81
2022-09-02 8:03 ` Markus Armbruster [this message]
2022-09-02 13:27 ` Hyman Huang
2022-09-01 17:22 ` [PATCH v1 3/8] migration: Introduce dirty-limit capability huangy81
2022-09-02 8:07 ` Markus Armbruster
2022-09-02 14:15 ` Hyman Huang
2022-09-05 9:32 ` Markus Armbruster
2022-09-05 13:13 ` Hyman Huang
2022-09-06 8:02 ` Markus Armbruster
2022-09-01 17:22 ` [PATCH v1 4/8] migration: Implement dirty-limit convergence algo huangy81
2022-09-06 20:37 ` Peter Xu
2022-09-08 14:35 ` Hyman
2022-09-08 14:47 ` Peter Xu
2022-09-08 14:59 ` Hyman Huang
2022-09-01 17:22 ` [PATCH v1 5/8] migration: Export dirty-limit time info huangy81
2022-10-01 18:31 ` Markus Armbruster
2022-10-02 1:13 ` Hyman Huang
2022-10-07 15:09 ` Markus Armbruster
2022-10-07 16:22 ` Hyman Huang
2022-09-01 17:22 ` [PATCH v1 6/8] tests: Add migration dirty-limit capability test huangy81
2022-09-01 17:22 ` [PATCH v1 7/8] tests/migration: Introduce dirty-ring-size option into guestperf huangy81
2022-09-01 17:22 ` [PATCH v1 8/8] tests/migration: Introduce dirty-limit " huangy81
2022-09-06 20:46 ` [PATCH v1 0/8] migration: introduce dirtylimit capability Peter Xu
2022-09-07 14:52 ` Hyman
2022-10-01 14:37 ` Markus Armbruster
2022-10-01 15:01 ` 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=875yi6xkwz.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=huangy81@chinatelecom.cn \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=thuth@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.