From: Derek Su <dereksu@qnap.com>
To: qemu-devel@nongnu.org
Cc: zhang.zhanghailiang@huawei.com, chyang@qnap.com,
quintela@redhat.com, Derek Su <dereksu@qnap.com>,
dgilbert@redhat.com, ctcheng@qnap.com, jwsu1986@gmail.com
Subject: [PATCH v1 0/1] COLO: migrate dirty ram pages before colo checkpoint
Date: Sun, 21 Jun 2020 10:10:03 +0800 [thread overview]
Message-ID: <20200621021004.5559-1-dereksu@qnap.com> (raw)
This series is to reduce the guest's downtime during colo checkpoint
by migrating dirty ram pages as many as possible before colo checkpoint.
If the iteration count reaches COLO_RAM_MIGRATE_ITERATION_MAX or
ram pending size is lower than 'x-colo-migrate-ram-threshold',
stop the ram migration and do colo checkpoint.
Test environment:
The both primary VM and secondary VM has 1GiB ram and 10GbE NIC
for FT traffic.
One fio buffer write job runs on the guest.
The result shows the total primary VM downtime is decreased by ~40%.
Please help to review it and suggestions are welcomed.
Thanks.
Derek Su (1):
migration/colo.c: migrate dirty ram pages before colo checkpoint
migration/colo.c | 79 ++++++++++++++++++++++++++++++++++++++++++
migration/migration.c | 20 +++++++++++
migration/trace-events | 2 ++
monitor/hmp-cmds.c | 8 +++++
qapi/migration.json | 18 ++++++++--
5 files changed, 125 insertions(+), 2 deletions(-)
--
2.17.1
next reply other threads:[~2020-06-21 2:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 2:10 Derek Su [this message]
2020-06-21 2:10 ` [PATCH v1 1/1] migration/colo.c: migrate dirty ram pages before colo checkpoint Derek Su
2020-06-22 17:23 ` Eric Blake
2020-07-13 9:03 ` Derek Su
2020-07-31 7:52 ` [PATCH v1 0/1] COLO: " Lukas Straub
2020-07-31 9:00 ` Zhanghailiang
2020-08-13 10:27 ` Derek Su
2020-08-15 1:41 ` Zhanghailiang
2020-08-15 2:45 ` Derek Su
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=20200621021004.5559-1-dereksu@qnap.com \
--to=dereksu@qnap.com \
--cc=chyang@qnap.com \
--cc=ctcheng@qnap.com \
--cc=dgilbert@redhat.com \
--cc=jwsu1986@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=zhang.zhanghailiang@huawei.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).