qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH] ram_save_live: add a no-progress convergence ru


From: Anthony Liguori
Subject: Re: [Qemu-devel] [PATCH] ram_save_live: add a no-progress convergence rule
Date: Tue, 19 May 2009 13:17:57 -0500
User-agent: Thunderbird 2.0.0.21 (X11/20090320)

Glauber Costa wrote:
On Tue, May 19, 2009 at 05:59:14PM +0300, Dor Laor wrote:
We can also make it configurable using the monitor migrate command. For example:
migrate -d -no_progress -threshold=x tcp:....
it can be done, but it fits better as a different monitor command

anthony, do you have any strong opinions here, or is this scheme acceptable?

Threshold is a bad metric. There's no way to choose a right number. If we were going to have a means to support metrics-based forced convergence (and I really think this belongs in libvirt) I'd rather see something based on bandwidth or wall clock time.

Let me put it this way, why 50? What were the guidelines for choosing that number and how would you explain what number a user should choose?

Regards,

Anthony Liguori




reply via email to

[Prev in Thread] Current Thread [Next in Thread]