From mboxrd@z Thu Jan 1 00:00:00 1970 From: Juergen Gross Subject: Re: [PATCH 6 of 8 [RFC]] libxc: introduce xc_domain_move_memory Date: Tue, 09 Apr 2013 07:23:48 +0200 Message-ID: <5163A5E4.6030608@ts.fujitsu.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Dario Faggioli Cc: dan.magenheimer@oracle.com, ian.campbell@citrix.com, George Dunlap , Andrew Cooper , Tim Deegan , Olaf Hering , xen-devel , David Vrabel , Keir Fraser , Andres Lagar-Cavilla , Jan Beulich , Roger Pau Monne List-Id: xen-devel@lists.xenproject.org On 09.04.2013 04:49, Dario Faggioli wrote: > as a mechanism of deallocating and reallocating (immediately!) _all_ > the memory of a domain. Notice it relies on the guest being suspended > already, before the function is invoked. Is this solution intended to be the final one? This might be okay for a domain with less than 1GB of memory, but I see problems for really huge domains. The needed time to copy the memory might result in long offline times. For this case something like live migration (optional?) would be a better solution, I think. Juergen -- Juergen Gross Principal Developer Operating Systems PBG PDG ES&S SWE OS6 Telephone: +49 (0) 89 3222 2967 Fujitsu Technology Solutions e-mail: juergen.gross@ts.fujitsu.com Domagkstr. 28 Internet: ts.fujitsu.com D-80807 Muenchen Company details: ts.fujitsu.com/imprint.html