From: Liran Schour <lirans@il.ibm.com>
To: qemu-devel@nongnu.org
Cc: Liran Schour <lirans@il.ibm.com>
Subject: [Qemu-devel] [PATCH v2 0/4] Reduce down time during migration without shared storage
Date: Thu, 21 Jan 2010 17:24:00 +0200 [thread overview]
Message-ID: <1264087444-14193-1-git-send-email-lirans@il.ibm.com> (raw)
This series of patches reduce the down time of the guest during a migration
without shared storage. It does that by start transfer dirty blocks in the
iterative phase. In the current code transferring of dirty blocks begins only
during the full phase while the guest is suspended. Therefore the guest will
be suspended linear to the amount of data that was written to disk during
migration.
Changes from v1: - infer storage performance by get_clock()
- remove dirty max iterations - user is responsible for migration convergence
- remove trailing whitespaces
- minor cleanups
block-migration.c | 244 +++++++++++++++++++++++++++++++++++------------------
block.c | 20 ++++-
block.h | 1 +
block_int.h | 1 +
4 files changed, 181 insertions(+), 85 deletions(-)
Signed-off-by: Liran Schour <lirans@il.ibm.com>
next reply other threads:[~2010-01-21 15:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 15:24 Liran Schour [this message]
2010-01-21 15:24 ` [Qemu-devel] [PATCH v2 1/4] Remove unused code Liran Schour
2010-01-21 15:24 ` [Qemu-devel] [PATCH v2 2/4] Tranfer dirty blocks during iterative phase Liran Schour
2010-01-21 15:24 ` [Qemu-devel] [PATCH v2 3/4] Count dirty blocks and expose an API to get dirty count Liran Schour
2010-01-21 15:24 ` [Qemu-devel] [PATCH v2 4/4] Try not to exceed max downtime on stage3 Liran Schour
2010-01-21 18:03 ` Pierre Riteau
2010-01-25 8:57 ` Liran Schour
2010-01-25 9:16 ` Pierre Riteau
2010-01-25 9:28 ` [Qemu-devel] [PATCH v2 0/4] Reduce down time during migration without shared storage Pierre Riteau
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=1264087444-14193-1-git-send-email-lirans@il.ibm.com \
--to=lirans@il.ibm.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).