From: Balamuruhan S <bala24@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: quintela@redhat.com, dgilbert@redhat.com, dgibson@redhat.com,
Balamuruhan S <bala24@linux.vnet.ibm.com>
Subject: [Qemu-devel] [PATCH v3 1/1] migration: calculate expected_downtime with ram_bytes_remaining()
Date: Wed, 25 Apr 2018 12:40:40 +0530 [thread overview]
Message-ID: <20180425071040.25542-2-bala24@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180425071040.25542-1-bala24@linux.vnet.ibm.com>
expected_downtime value is not accurate with dirty_pages_rate * page_size,
using ram_bytes_remaining would yeild it correct. It will initially be a
gross over-estimate, but for for non-converging migrations it should
approach a reasonable estimate later on.
currently bandwidth and expected_downtime value are calculated in
migration_update_counters() during each iteration from
migration_thread(), where as remaining ram is calculated in
qmp_query_migrate() when we actually call "info migrate". Due to this
there is some difference in expected_downtime value being calculated.
with this patch bandwidth, expected_downtime and remaining ram are
calculated in migration_update_counters(), retrieve the same value during
"info migrate". By this approach we get almost close enough value.
Reported-by: Michael Roth <mdroth@linux.vnet.ibm.com>
Signed-off-by: Balamuruhan S <bala24@linux.vnet.ibm.com>
---
migration/migration.c | 11 ++++++++---
migration/migration.h | 1 +
2 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/migration/migration.c b/migration/migration.c
index 52a5092add..5d721ee481 100644
--- a/migration/migration.c
+++ b/migration/migration.c
@@ -614,7 +614,7 @@ static void populate_ram_info(MigrationInfo *info, MigrationState *s)
}
if (s->state != MIGRATION_STATUS_COMPLETED) {
- info->ram->remaining = ram_bytes_remaining();
+ info->ram->remaining = s->ram_bytes_remaining;
info->ram->dirty_pages_rate = ram_counters.dirty_pages_rate;
}
}
@@ -2227,6 +2227,7 @@ static void migration_update_counters(MigrationState *s,
transferred = qemu_ftell(s->to_dst_file) - s->iteration_initial_bytes;
time_spent = current_time - s->iteration_start_time;
bandwidth = (double)transferred / time_spent;
+ s->ram_bytes_remaining = ram_bytes_remaining();
s->threshold_size = bandwidth * s->parameters.downtime_limit;
s->mbps = (((double) transferred * 8.0) /
@@ -2237,8 +2238,12 @@ static void migration_update_counters(MigrationState *s,
* recalculate. 10000 is a small enough number for our purposes
*/
if (ram_counters.dirty_pages_rate && transferred > 10000) {
- s->expected_downtime = ram_counters.dirty_pages_rate *
- qemu_target_page_size() / bandwidth;
+ /*
+ * It will initially be a gross over-estimate, but for for
+ * non-converging migrations it should approach a reasonable estimate
+ * later on
+ */
+ s->expected_downtime = s->ram_bytes_remaining / bandwidth;
}
qemu_file_reset_rate_limit(s->to_dst_file);
diff --git a/migration/migration.h b/migration/migration.h
index 8d2f320c48..8584f8e22e 100644
--- a/migration/migration.h
+++ b/migration/migration.h
@@ -128,6 +128,7 @@ struct MigrationState
int64_t downtime_start;
int64_t downtime;
int64_t expected_downtime;
+ int64_t ram_bytes_remaining;
bool enabled_capabilities[MIGRATION_CAPABILITY__MAX];
int64_t setup_time;
/*
--
2.14.3
next prev parent reply other threads:[~2018-04-25 7:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 7:10 [Qemu-devel] [PATCH v3 0/1] migration: calculate expected_downtime with ram_bytes_remaining() Balamuruhan S
2018-04-25 7:10 ` Balamuruhan S [this message]
2018-05-01 14:37 ` [Qemu-devel] [PATCH v3 1/1] " Balamuruhan S
2018-05-16 13:43 ` Laurent Vivier
2018-05-22 11:33 ` Balamuruhan S
2018-06-08 18:24 ` Laurent Vivier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180425071040.25542-2-bala24@linux.vnet.ibm.com \
--to=bala24@linux.vnet.ibm.com \
--cc=dgibson@redhat.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).