| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
RE: [Xen-devel] [PATCH] linux/balloon:don't allow ballooningdowna domain
Hmmm... it appears to me that minimum_target() doesn't
work when balloon.c is built as a module (always returns 0).
Can you confirm/deny?
Also, still hoping to get more info on the algorithm
used in minimum_target().
Thanks,
Dan
> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx]On Behalf Of Jan Beulich
> Sent: Friday, May 02, 2008 1:31 PM
> To: dan.magenheimer@xxxxxxxxxx
> Cc: Ky Srinivasan; xen-devel@xxxxxxxxxxxxxxxxxxx;
> keir.fraser@xxxxxxxxxxxxx; garloff@xxxxxxx
> Subject: RE: [Xen-devel] [PATCH] linux/balloon:don't allow
> ballooningdowna domain below a reasonable limit
>
>
> >>> "Dan Magenheimer" <dan.magenheimer@xxxxxxxxxx> 05/01/08
> 2:00 AM >>>
> >OK, I think I am understanding it a bit better:
> >the max_pfn part is just adding in some "slop"
> >which is a fraction of total main memory which
> >is growing smaller (roughly logarithmically)
> >as memory grows larger. I'm still not sure about
> >the magic values in MB2PAGES though... I'm guessing
> >these were gathered somehow experimentally?
>
> I have to defer to the original author here - Kurt?
>
> >With the "divide result of your algorithm by two",
> >I was able to get thirteen 512MB domains (idle
> >for now) running on a 2GB system.
>
> You mean ballooned-down domains, right? Perhaps using your
> self-ballooning change? I have to admit I'm a little nervous
> about attempting to overcommit memory in this way in a
> production environment, but as long as this depends on a
> decision of the operator it's certainly a good option to have.
>
> Jan
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home