From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Chulmin Kim <cmkim@core.kaist.ac.kr>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: maximum memory size allocated by _xmalloc
Date: Wed, 11 Jul 2012 10:48:54 +0100 [thread overview]
Message-ID: <4FFD4C06.7090403@citrix.com> (raw)
In-Reply-To: <008601cd5f45$6eff7530$4cfe5f90$@core.kaist.ac.kr>
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
next prev parent reply other threads:[~2012-07-11 9:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 9:13 maximum memory size allocated by _xmalloc Chulmin Kim
2012-07-11 9:48 ` Andrew Cooper [this message]
2012-07-12 0:01 ` Chulmin Kim
2012-07-12 9:07 ` Andrew Cooper
2012-07-12 9:24 ` FW: " Chulmin Kim
2012-08-13 8:08 ` Chulmin Kim
-- strict thread matches above, loose matches on Subject: below --
2012-07-12 9:28 Chulmin Kim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FFD4C06.7090403@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=cmkim@core.kaist.ac.kr \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.