From: Balamuruhan S <bala24@linux.vnet.ibm.com>
To: Juan Quintela <quintela@redhat.com>
Cc: qemu-devel@nongnu.org,
Qemu-devel
<qemu-devel-bounces+bala24=linux.vnet.ibm.com@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] migration: calculate expected_downtime with ram_bytes_remaining()
Date: Tue, 10 Apr 2018 16:22:18 +0530 [thread overview]
Message-ID: <13ace01d09a7c869572669db763de115@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180410095233.GA11713@localhost.localdomain>
On 2018-04-10 15:22, Balamuruhan S wrote:
> On Wed, Apr 04, 2018 at 11:04:59AM +0200, Juan Quintela wrote:
>> Balamuruhan S <bala24@linux.vnet.ibm.com> wrote:
>> > expected_downtime value is not accurate with dirty_pages_rate * page_size,
>> > using ram_bytes_remaining would yeild it correct.
>> >
>> > Signed-off-by: Balamuruhan S <bala24@linux.vnet.ibm.com>
>>
>> Reviewed-by: Juan Quintela <quintela@redhat.com>
>>
>> See my other mail on the thread, my understanding is that your change
>> is
>> corret (TM).
>
> Juan, Please help to merge it.
Sorry for asking it as during discussion going on, but the reason is
currently
postcopy migration for HP backed P8 guest from P8 -> P9 is broken and to
use
precopy with appropriate downtime value we need this patch to be
backported
to distros that is to be released soon.
>
> Regards,
> Bala
>
>>
>> Thanks, Juan.
>>
>> > ---
>> > migration/migration.c | 3 +--
>> > 1 file changed, 1 insertion(+), 2 deletions(-)
>> >
>> > diff --git a/migration/migration.c b/migration/migration.c
>> > index 58bd382730..4e43dc4f92 100644
>> > --- a/migration/migration.c
>> > +++ b/migration/migration.c
>> > @@ -2245,8 +2245,7 @@ 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;
>> > + s->expected_downtime = ram_bytes_remaining() / bandwidth;
>> > }
>> >
>> > qemu_file_reset_rate_limit(s->to_dst_file);
>>
next prev parent reply other threads:[~2018-04-10 10:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-31 18:55 [Qemu-devel] [PATCH] migration: calculate expected_downtime with ram_bytes_remaining() Balamuruhan S
2018-04-03 6:10 ` Peter Xu
2018-04-03 17:30 ` bala24
2018-04-04 1:59 ` Peter Xu
2018-04-04 9:02 ` Juan Quintela
2018-04-04 9:04 ` Juan Quintela
2018-04-10 9:52 ` Balamuruhan S
2018-04-10 10:52 ` Balamuruhan S [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-04-04 6:25 Balamuruhan S
2018-04-04 8:06 ` Peter Xu
2018-04-04 8:49 ` Balamuruhan S
2018-04-09 18:57 ` Dr. David Alan Gilbert
2018-04-10 1:22 ` David Gibson
2018-04-10 10:02 ` Dr. David Alan Gilbert
2018-04-11 1:28 ` David Gibson
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=13ace01d09a7c869572669db763de115@linux.vnet.ibm.com \
--to=bala24@linux.vnet.ibm.com \
--cc=qemu-devel-bounces+bala24=linux.vnet.ibm.com@nongnu.org \
--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).