From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: maximum memory size allocated by _xmalloc Date: Wed, 11 Jul 2012 10:48:54 +0100 Message-ID: <4FFD4C06.7090403@citrix.com> References: <008601cd5f45$6eff7530$4cfe5f90$@core.kaist.ac.kr> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <008601cd5f45$6eff7530$4cfe5f90$@core.kaist.ac.kr> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Chulmin Kim Cc: "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On 11/07/12 10:13, Chulmin Kim wrote: > Hi all, > > I'm currently inserting my own code to adjust the several existing memory > ballooning works. > > To accomplish it, I manage some kind of statistics in Xen memory area. > > Using _xmalloc, I've allocated certain size of memory chunk for the data > structure. ( I varied it from 10kb to 24 MB.) > > When the size is equal to 24 MB, xen won't boot anymore. (stuck during the > xmalloc, according to my debugging. _xmalloc returns NULL.) > There was no problem when the size is below 12MB. > > Is there any limitation such as max memory size for _xmalloc? > > I suspected xen heap size, but, it is no longer adjustable. Right? > > I hope somebody can give me a clue. Thanks. _xmalloc will first try to use the size pools for allocation, and failing that, try to allocate full pages. As it is returning NULL, this probably means you no longer have 24MB of free contiguous RAM to allocate. ~Andrew > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel -- Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer T: +44 (0)1223 225 900, http://www.citrix.com