From: Anthony Liguori <anthony@codemonkey.ws>
To: Liran Schour <LIRANS@il.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Add iterative phase to qemu_savevm_state to allow live storage migration
Date: Wed, 21 Oct 2009 13:30:17 -0500 [thread overview]
Message-ID: <4ADF5339.1000004@codemonkey.ws> (raw)
In-Reply-To: <OF0A1AA327.F6057BC3-ONC2257655.00352299-C2257655.003BFB52@il.ibm.com>
Liran Schour wrote:
> qemu_savevm_state will call all registered components with 3 phases: START,
> PART, END. Only the PART phase is iterative.
> In case of storage live migration we have lot more data to copy then memory
> and usually the dirty rate is much less then memory dirty rate. I thought
> about adding an iterative phase before PART for iterating massive data
> transfer that we want to transfer before starting to transfer memory data.
> The new phase will be iterative and will step to the next phase only when
> all registered components will agree.
>
I think we'll eventually want to generalize this but for now, having
PART1 and PART2 is not a bad idea.
Regards,
Anthony Liguori
> What do you think?
>
> - Liran
>
>
>
>
prev parent reply other threads:[~2009-10-21 18:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 10:57 [Qemu-devel] Add iterative phase to qemu_savevm_state to allow live storage migration Liran Schour
2009-10-21 18:30 ` Anthony Liguori [this message]
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=4ADF5339.1000004@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.