From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hongyang Yang Subject: Re: [PATCH v6 0/13] Migration Stream v2 Date: Wed, 9 Jul 2014 14:01:55 +0800 Message-ID: <53BCDAD3.5050602@cn.fujitsu.com> References: <1404754682-28379-1-git-send-email-andrew.cooper3@citrix.com> <20140708163550.GA9857@laptop.dumpdata.com> <53BC2BDF.40700@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <53BC2BDF.40700@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Andrew Cooper , Konrad Rzeszutek Wilk Cc: Keir Fraser , Ian Campbell , Tim Deegan , Ian Jackson , Xen-devel , Frediano Ziglio , David Vrabel , Jan Beulich List-Id: xen-devel@lists.xenproject.org Hi Andrew, On 07/09/2014 01:35 AM, Andrew Cooper wrote: > On 08/07/14 17:35, Konrad Rzeszutek Wilk wrote: >> On Mon, Jul 07, 2014 at 06:37:49PM +0100, Andrew Cooper wrote: >>> Hello, >>> >>> Presented here for review is v6 of the Migration Stream v2 work. >>> >>> v6 follows the integration of this code into XenServer, and having the full >>> suite of XenRT tests being run. Included in these tests are live migrations >>> from 32bit toolstacks to 64bit toolstacks, using the python conversion script. >>> Several corruption issues have been located and fixed, as well as many minor >>> improvements. >>> >>> In addition, performance tests have been performed. After finding an initial >>> regression, the code uas been tweaked to use writev() in preference to >>> write() which vastly reduces the number of system calls performed. The >>> performance is now better than the legacy code for all sizes of VM. >> Fantastic! >> >> .. snip.. >>> The code is presented here for comment/query/critism. >> My notes say: 'tmem and remus need work'. Is that addressed by this >> patchset or would that be further work? >> >> Thank you. > > tmem still completely outstanding. > > remus is being worked on by Yang (which is fantastic from my point of > view). I believe this is a PoC apparently working? Do you mean a PoC of remus support on migration v2? If so, yes, I will post a RFC patch on this. BTW, will migration v2 be in Xen 4.5(both libxc and libxl side)? If it will be in Xen 4.5, will legacy migration be completely removed from 4.5 or both versions of migration will co-exist for a period? > > ~Andrew > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel > -- Thanks, Yang.