qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Franciosi <felipe@nutanix.com>
To: Peter Xu <peterx@redhat.com>, Juan Quintela <quintela@redhat.com>,
	"Jason J. Herne" <jjherne@linux.vnet.ibm.com>,
	amit Shah <amit.shah@redhat.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Malcolm Crossley <malcolm@nutanix.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Felipe Franciosi <felipe@nutanix.com>
Subject: [Qemu-devel] [PATCH 3/4] migration: set bytes_xfer_* outside of autoconverge logic
Date: Wed, 24 May 2017 17:10:02 +0100	[thread overview]
Message-ID: <1495642203-12702-4-git-send-email-felipe@nutanix.com> (raw)
In-Reply-To: <1495642203-12702-1-git-send-email-felipe@nutanix.com>

The bytes_xfer_now/prev counters are only used by the auto convergence
logic. However, they are used alongside the dirty_pages_rate counter,
which is calculated (and required) outside of this logic. The problem
with this approach is that if the auto convergence capability is changed
while a migration is ongoing, the relationship of the counters will be
broken.

This moves the management of bytes_xfer_now/prev counters outside of the
auto convergence logic to address this issue.

Signed-off-by: Felipe Franciosi <felipe@nutanix.com>
---
 migration/ram.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/migration/ram.c b/migration/ram.c
index 495ecbe..1a3d9e6 100644
--- a/migration/ram.c
+++ b/migration/ram.c
@@ -697,6 +697,7 @@ static void migration_bitmap_sync(RAMState *rs)
         /* calculate period counters */
         rs->dirty_pages_rate = rs->num_dirty_pages_period * 1000
             / (end_time - rs->time_last_bitmap_sync);
+        bytes_xfer_now = ram_bytes_transferred();
 
         if (migrate_auto_converge()) {
             /* The following detection logic can be refined later. For now:
@@ -704,7 +705,6 @@ static void migration_bitmap_sync(RAMState *rs)
                amount of bytes that just got transferred since the last time we
                were in this routine. If that happens twice, start or increase
                throttling */
-            bytes_xfer_now = ram_bytes_transferred();
 
             if ((rs->num_dirty_pages_period * TARGET_PAGE_SIZE >
                    (bytes_xfer_now - rs->bytes_xfer_prev) / 2) &&
@@ -713,7 +713,6 @@ static void migration_bitmap_sync(RAMState *rs)
                     rs->dirty_rate_high_cnt = 0;
                     mig_throttle_guest_down();
             }
-            rs->bytes_xfer_prev = bytes_xfer_now;
         }
 
         if (migrate_use_xbzrle()) {
@@ -730,6 +729,7 @@ static void migration_bitmap_sync(RAMState *rs)
         /* reset period counters */
         rs->time_last_bitmap_sync = end_time;
         rs->num_dirty_pages_period = 0;
+        rs->bytes_xfer_prev = bytes_xfer_now;
     }
     if (migrate_use_events()) {
         qapi_event_send_migration_pass(rs->bitmap_sync_count, NULL);
-- 
1.9.5

  parent reply	other threads:[~2017-05-24 16:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-24 16:09 [Qemu-devel] [PATCH 0/4] migration: autoconverge counter fixes Felipe Franciosi
2017-05-24 16:10 ` [Qemu-devel] [PATCH 1/4] migration: keep bytes_xfer_prev init'd to zero Felipe Franciosi
2017-05-25  0:50   ` Peter Xu
2017-05-30 16:14   ` Juan Quintela
2017-05-24 16:10 ` [Qemu-devel] [PATCH 2/4] migration: set dirty_pages_rate before autoconverge logic Felipe Franciosi
2017-05-25  0:40   ` Peter Xu
2017-05-25 10:52     ` Felipe Franciosi
2017-05-25 11:10       ` Peter Xu
2017-05-30 16:14   ` Juan Quintela
2017-05-24 16:10 ` Felipe Franciosi [this message]
2017-05-25  0:40   ` [Qemu-devel] [PATCH 3/4] migration: set bytes_xfer_* outside of " Peter Xu
2017-05-30 16:14   ` Juan Quintela
2017-05-24 16:10 ` [Qemu-devel] [PATCH 4/4] migration: use dirty_rate_high_cnt more aggressively Felipe Franciosi
2017-05-24 16:25   ` Daniel P. Berrange
2017-05-24 16:36     ` Felipe Franciosi
2017-05-25  1:03   ` Peter Xu
2017-05-25 11:20     ` Felipe Franciosi
2017-05-26  2:45       ` Peter Xu
2017-05-30 16:17   ` Juan Quintela

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=1495642203-12702-4-git-send-email-felipe@nutanix.com \
    --to=felipe@nutanix.com \
    --cc=amit.shah@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=jjherne@linux.vnet.ibm.com \
    --cc=malcolm@nutanix.com \
    --cc=peterx@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).