I missed something... ~hyman <hy...@git.sr.ht> writes:
> From: Hyman Huang(黄勇) <yong.hu...@smartx.com> > > Introduce "x-vcpu-dirty-limit-period" migration experimental > parameter, which is in the range of 1 to 1000ms and used to > make dirty page rate calculation period configurable. > > Currently with the "x-vcpu-dirty-limit-period" varies, the > total time of live migration changes, test results show the > optimal value of "x-vcpu-dirty-limit-period" ranges from > 500ms to 1000 ms. "x-vcpu-dirty-limit-period" should be made > stable once it proves best value can not be determined with > developer's experiments. > > Signed-off-by: Hyman Huang(黄勇) <yong.hu...@smartx.com> > Reviewed-by: Markus Armbruster <arm...@redhat.com> > Reviewed-by: Juan Quintela <quint...@redhat.com> [...] > diff --git a/qapi/migration.json b/qapi/migration.json > index 47dfef0278..363055d252 100644 > --- a/qapi/migration.json > +++ b/qapi/migration.json > @@ -789,9 +789,14 @@ > # Nodes are mapped to their block device name if there is one, and > # to their node name otherwise. (Since 5.2) > # > +# @x-vcpu-dirty-limit-period: Periodic time (in milliseconds) of dirty > +# limit during live migration. Should be in the range 1 to 1000ms, > +# defaults to 1000ms. (Since 8.1) You need to adjust all the "Since" tags to 8.2. [...]
