From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1N0fx6-0006jc-9n
	for qemu-devel@nongnu.org; Wed, 21 Oct 2009 14:30:28 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1N0fx1-0006hA-JG
	for qemu-devel@nongnu.org; Wed, 21 Oct 2009 14:30:27 -0400
Received: from [199.232.76.173] (port=60665 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1N0fx1-0006gx-CH
	for qemu-devel@nongnu.org; Wed, 21 Oct 2009 14:30:23 -0400
Received: from mail-ew0-f221.google.com ([209.85.219.221]:57792)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1N0fx1-0008Tm-0A
	for qemu-devel@nongnu.org; Wed, 21 Oct 2009 14:30:23 -0400
Received: by ewy21 with SMTP id 21so5568377ewy.8
	for <qemu-devel@nongnu.org>; Wed, 21 Oct 2009 11:30:22 -0700 (PDT)
Message-ID: <4ADF5339.1000004@codemonkey.ws>
Date: Wed, 21 Oct 2009 13:30:17 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Add iterative phase to qemu_savevm_state to allow
	live storage migration
References: <OF0A1AA327.F6057BC3-ONC2257655.00352299-C2257655.003BFB52@il.ibm.com>
In-Reply-To: <OF0A1AA327.F6057BC3-ONC2257655.00352299-C2257655.003BFB52@il.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Liran Schour <LIRANS@il.ibm.com>
Cc: qemu-devel@nongnu.org

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
>
>
>
>