From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
"Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
Daniel Kiper <dkiper@net-space.pl>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Ballooning up
Date: Tue, 07 Sep 2010 23:26:04 +1000 [thread overview]
Message-ID: <4C863D6C.3050105@goop.org> (raw)
In-Reply-To: <1283854445.14311.91.camel@zakaz.uk.xensource.com>
On 09/07/2010 08:14 PM, Ian Campbell wrote:
> On Tue, 2010-09-07 at 09:36 +0100, Jeremy Fitzhardinge wrote:
>> I finally got around to implementing "ballooning up" in the pvops
>> kernels. Now if you start a domain with "memory=X maxmem=Y", the domain
>> will start with X MB of memory, but you can use "x[ml] mem-set" to
>> expand the domain up to Y.
> Cool. What did the issue with plymouth and friends turn out to be?
>
It was totalram_pages getting decremented when pages were being appended
to the balloon, even though those pages were never counted. So it got
very low, and while it isn't actually used to account for how much free
memory there is, some random pieces of code use something based on it to
get a rough metric for free memory and block waiting for it to go up, or
EAGAIN (or something).
It was a bit hard to directly observe because totalram_pages doesn't get
displayed directly in /proc/meminfo, but removing the decrement showed
that was the problem.
J
next prev parent reply other threads:[~2010-09-07 13:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 8:36 Ballooning up Jeremy Fitzhardinge
[not found] ` <54eebb3a-f539-43be-8134-a969a4f671c4@default4C8EAB0E.7040407@goop.org>
2010-09-07 10:14 ` Ian Campbell
2010-09-07 13:26 ` Jeremy Fitzhardinge [this message]
2010-09-07 14:10 ` Ian Campbell
2010-09-15 21:47 ` Dan Magenheimer
2010-09-15 22:41 ` Jeremy Fitzhardinge
2010-09-13 21:17 ` Dan Magenheimer
2010-09-13 21:39 ` Dan Magenheimer
2010-09-13 23:06 ` Jeremy Fitzhardinge
2010-09-13 22:51 ` Jeremy Fitzhardinge
2010-09-14 0:22 ` Dan Magenheimer
2010-09-14 0:46 ` Jeremy Fitzhardinge
2010-09-14 15:06 ` Dan Magenheimer
2010-09-14 22:05 ` Jeremy Fitzhardinge
2010-09-15 7:13 ` Ian Campbell
2010-09-14 8:41 ` Jan Beulich
2010-09-14 16:35 ` Jeremy Fitzhardinge
2010-09-14 9:07 ` Ian Campbell
2010-09-14 16:42 ` Jeremy Fitzhardinge
2010-09-15 7:10 ` Ian Campbell
2010-09-15 17:29 ` Jeremy Fitzhardinge
2010-09-15 18:06 ` Dan Magenheimer
2010-09-15 20:29 ` Jeremy Fitzhardinge
2010-09-14 8:34 ` Ian Campbell
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=4C863D6C.3050105@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Campbell@citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=Xen-devel@lists.xensource.com \
--cc=dan.magenheimer@oracle.com \
--cc=dkiper@net-space.pl \
--cc=konrad.wilk@oracle.com \
/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.