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 0/4] migration: autoconverge counter fixes
Date: Wed, 24 May 2017 17:09:59 +0100 [thread overview]
Message-ID: <1495642203-12702-1-git-send-email-felipe@nutanix.com> (raw)
As discussed in the ML [1], there are some issues around the way ram.c accounts
for transferred data and dirty pages for the auto convergence calculations. The
patches in these series fix that by:
- Keeping bytes_xfer_prev zeroed until it's used
- Ensure bytes_xfer_* counters are accounted for the same period as
dirty_pages_* counters
- Start throttling in a consistent manner
[1] http://lists.nongnu.org/archive/html/qemu-devel/2017-05/msg05524.html
Felipe Franciosi (4):
migration: keep bytes_xfer_prev init'd to zero
migration: set dirty_pages_rate before autoconverge logic
migration: set bytes_xfer_* outside of autoconverge logic
migration: use dirty_rate_high_cnt more aggressively
migration/ram.c | 23 +++++++++++------------
1 file changed, 11 insertions(+), 12 deletions(-)
--
1.9.5
next 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 Felipe Franciosi [this message]
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 ` [Qemu-devel] [PATCH 3/4] migration: set bytes_xfer_* outside of " Felipe Franciosi
2017-05-25 0:40 ` 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-1-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).