From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Load increase after memory upgrade (part2) Date: Thu, 14 Jun 2012 14:31:52 -0400 Message-ID: <20120614183152.GC21956@phenom.dumpdata.com> References: <20120511194138.GA30099@phenom.dumpdata.com> <20120613165529.GA10986@phenom.dumpdata.com> <4FD9A307.9030203@cantab.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <4FD9A307.9030203@cantab.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: David Vrabel Cc: Konrad Rzeszutek Wilk , xen-devel , Carsten Schiers , Jan Beulich , Sander Eikelenboom List-Id: xen-devel@lists.xenproject.org On Thu, Jun 14, 2012 at 09:38:31AM +0100, David Vrabel wrote: > On 13/06/12 17:55, Konrad Rzeszutek Wilk wrote: > > > > + /* 3. Do the exchange for non-contiguous MFNs. */ > > + success = xen_exchange_memory(n, 0 /* this is always called per page */, in_frames, > > + n, 0, out_frames, address_bits); > > vmalloc() does not require physically contiguous MFNs. It doesn't matter that much in this context as the vmalloc calls this per-page - so it is only one page that is swizzled. > > David