From: bala24@linux.vnet.ibm.com
To: qemu-devel@nongnu.org
Cc: david@gibson.dropbear.id.au, dgilbert@redhat.com,
peterx@redhat.com, Balamuruhan S <bala24@linux.vnet.ibm.com>
Subject: [Qemu-devel] [PATCH 0/1] migration: calculate expected_downtime considering redirtied ram
Date: Tue, 22 Jan 2019 20:35:42 +0530 [thread overview]
Message-ID: <20190122150543.16889-1-bala24@linux.vnet.ibm.com> (raw)
From: Balamuruhan S <bala24@linux.vnet.ibm.com>
Based on the discussion with Dave and David Gibson earlier with respect
to expected_downtime calculation,
https://lists.gnu.org/archive/html/qemu-devel/2018-04/msg02418.html
got suggestions that the calculation is of not accurate and we need to
consider the ram that gets redirtied during the time when we would have
actually transferred ram in the current iteration.
so I have came up with a calculation by considering the ram that could
get redirtied during the current iteration at the time we would have
transferred the remaining ram in current iteration. By this way,
the total ram to be transferred will be remaining ram + redirtied ram
and dividing with bandwidth would yield us better expected_downtime
value.
Please help to review and suggest about this approach.
Balamuruhan S (1):
migration: calculate expected_downtime considering redirtied ram
migration/migration.c | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
--
2.14.5
next reply other threads:[~2019-01-22 18:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 15:05 bala24 [this message]
2019-01-22 15:05 ` [Qemu-devel] [PATCH 1/1] migration: calculate expected_downtime considering redirtied ram bala24
2019-01-23 16:35 ` Juan Quintela
2019-01-24 7:18 ` Peter Xu
2019-01-30 9:16 ` Balamuruhan S
2019-02-02 22:05 ` [Qemu-devel] [PATCH 0/1] " no-reply
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=20190122150543.16889-1-bala24@linux.vnet.ibm.com \
--to=bala24@linux.vnet.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=dgilbert@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).