Re: [Xen-devel] Kernel 3.11 / 3.12 OOM killer and Xen ballooning

[Daniel Kiper <daniel.kiper@xxxxxxxxxx>]

On Mon, Feb 03, 2014 at 11:20:33AM +0000, James Dingwall wrote:
> Daniel Kiper wrote:

[...]

> >Hmmm... James, how do you build webkit-gtk? Just simple "make" or "make -j"?
> >Could you confirm that webkit-gtk in any "subjobs" do not use "make -j"?
> My guest domain is Gentoo and I have MAKEOPTS="-j2" set in make.conf
> and according to the build log for webkit-gtk this is used
> unchanged:
> >>> Source configured.
> >>> Compiling source in
> /var/tmp/portage/net-libs/webkit-gtk-2.0.4/work/webkitgtk-2.0.4 ...
> make -j2
>
> I wouldn't read anything in particular to it being webkit as I have
> seen similar from other large compiles (gcc, glibc, kdelibs, ...)

Thanks, it makes sens. I was afraid that somewhere "make -j" without
an argument has been called.

> >>>>But I think from the beginning tmem/balloon driver can't expand guest
> >>>>memory from size 'memory' to 'maxmem' automatically.
> >>>I am carrying this patch for libxl (4.3.1) because maxmem wasn't
> >>>being honoured.
> >James, what do you mean by "maxmem wasn't being honoured"?
> http://lists.xen.org/archives/html/xen-devel/2013-10/msg02228.html -
> the guest would never balloon above the value of memory when maxmem
> was set and was > memory in the configuration file.  There were some
> discussions about the correctness of this patch but the only place I
> could see an impact of maxmem was the parsing of the config
> parameters for the setup of the guest domain. IIRC the xl mem-max
> command which changes the same parameter once the guest domain is
> running resulted with the balloon up behaviour to max-mem working as
> expected. So the discrepancy between how xl behaves with the maxmem
> in the config or the execution of xl mem-max was what I had noted
> and what this patch resolved.  It would be easy to repeat those
> tests if necessary.

Please look for "[PATCH v4 0/4] libxl: memory management patches",
"[PATCH v2 0/2] xen/balloon: Extension and fix" and earlier related
threads. They contain almost hammered out and agreed solution for
this issue (you also find explanation for this xl behavior; note that
xm behavior was different). However, I was not able to finish this
patches due to other stuff on my plate. I have still this issue on
my todo list. If you would like to work on these patches go ahead.
I am happy to help but I am not able to work on them right now.

Daniel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel