[Qemu-devel] [PATCH 1/4] migration: change initial value of expected_downtime
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 quint...@redhat.com Reviewed-by: Orit Wasserman owass...@redhat.com --- migration.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/migration.c b/migration.c index b1ebb01..b3f5ba4 100644 --- a/migration.c +++ b/migration.c @@ -774,6 +774,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/100; s-xfer_limit = s-bandwidth_limit / XFER_LIMIT_RATIO; s-complete = false; -- 1.8.1.2
Re: [Qemu-devel] [PATCH 1/4] migration: change initial value of expected_downtime
On 02/01/2013 02:32 PM, Juan Quintela wrote: 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 quint...@redhat.com --- 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/100; s-xfer_limit = s-bandwidth_limit / XFER_LIMIT_RATIO; s-complete = false; Reviewed-by: Orit Wasserman owass...@redhat.com
[Qemu-devel] [PATCH 1/4] migration: change initial value of expected_downtime
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 quint...@redhat.com --- 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/100; s-xfer_limit = s-bandwidth_limit / XFER_LIMIT_RATIO; s-complete = false; -- 1.8.1
