~hyman <hy...@git.sr.ht> wrote: > 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
milliseconds > make dirtyrate 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> > Signed-off-by: Markus Armbruster <arm...@redhat.com> > +#define DEFAULT_MIGRATE_VCPU_DIRTY_LIMIT_PERIOD 1000 /* microsecond */ > + microseconds I guess that the problem is the comment. I can fix it when pulling it. Reviewed-by: Juan Quintela <quint...@redhat.com>
