From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:58149) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U1Fni-0005UQ-8D for qemu-devel@nongnu.org; Fri, 01 Feb 2013 07:33:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U1Fnh-0000N3-8U for qemu-devel@nongnu.org; Fri, 01 Feb 2013 07:33:02 -0500 Received: from mx1.redhat.com ([209.132.183.28]:55514) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U1Fnh-0000Mr-1u for qemu-devel@nongnu.org; Fri, 01 Feb 2013 07:33:01 -0500 From: Juan Quintela Date: Fri, 1 Feb 2013 13:32:53 +0100 Message-Id: <1359721976-19238-2-git-send-email-quintela@redhat.com> In-Reply-To: <1359721976-19238-1-git-send-email-quintela@redhat.com> References: <1359721976-19238-1-git-send-email-quintela@redhat.com> Subject: [Qemu-devel] [PATCH 1/4] migration: change initial value of expected_downtime List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Qemu Devel , Anthony Liguori 0 is a very bad initial value, what we are trying to get is max_downtime, so that is a much better estimation. Signed-off-by: Juan Quintela --- migration.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/migration.c b/migration.c index 77c1971..d86946e 100644 --- a/migration.c +++ b/migration.c @@ -782,6 +782,8 @@ void migrate_fd_connect(MigrationState *s) s->buffer = NULL; s->buffer_size = 0; s->buffer_capacity = 0; + /* This is a best 1st approximation. ns to ms */ + s->expected_downtime = max_downtime/1000000; s->xfer_limit = s->bandwidth_limit / XFER_LIMIT_RATIO; s->complete = false; -- 1.8.1