On Fri, Aug 2, 2019 at 1:59 PM Wei Yang wrote:
>
> On Fri, Aug 02, 2019 at 01:46:41PM +0800, Ivan Ren wrote:
> > s->iteration_start_time = qemu_clock_get_ms(QEMU_CLOCK_REALTIME);
> >+/*
> >+ * Update s->iteration_initial_bytes to match
> >>>s->iteration_start_time.
>
On Fri, Aug 02, 2019 at 01:46:41PM +0800, Ivan Ren wrote:
> s->iteration_start_time = qemu_clock_get_ms(QEMU_CLOCK_REALTIME);
>+/*
>+ * Update s->iteration_initial_bytes to match
>>>s->iteration_start_time.
>+ */
>+s->iteration_initial_bytes =
s->iteration_start_time = qemu_clock_get_ms(QEMU_CLOCK_REALTIME);
+/*
+ * Update s->iteration_initial_bytes to match
>>s->iteration_start_time.
+ */
+s->iteration_initial_bytes = migration_total_bytes(s);
>>>
>>>Is this one necessary? We have sent out
On Thu, Aug 01, 2019 at 04:10:34PM +0800, Ivan Ren wrote:
>>> s->iteration_start_time = qemu_clock_get_ms(QEMU_CLOCK_REALTIME);
>>>+/*
>>>+ * Update s->iteration_initial_bytes to match
>s->iteration_start_time.
>>>+ */
>>>+s->iteration_initial_bytes = migration_total_bytes(s);
>> s->iteration_start_time = qemu_clock_get_ms(QEMU_CLOCK_REALTIME);
>>+/*
>>+ * Update s->iteration_initial_bytes to match
s->iteration_start_time.
>>+ */
>>+s->iteration_initial_bytes = migration_total_bytes(s);
>
>Is this one necessary? We have sent out nothing yet.
Yes,
On Tue, Jul 30, 2019 at 01:36:32PM +0800, Ivan Ren wrote:
>From: Ivan Ren
>
>This patch fix a multifd migration bug in migration speed calculation, this
>problem can be reproduced as follows:
>1. start a vm and give a heavy memory write stress to prevent the vm be
> successfully migrated to
Ivan Ren wrote:
> From: Ivan Ren
>
> This patch fix a multifd migration bug in migration speed calculation, this
> problem can be reproduced as follows:
> 1. start a vm and give a heavy memory write stress to prevent the vm be
>successfully migrated to destination
> 2. begin a migration with
