On Sun, 22 May 2011, Gordon Henderson wrote: > > I think this has been on the list before, but my arching search is > failling me... I've got containers working with memory limitations using > > lxc.cgroup.memory.limit_in_bytes > and > lxc.cgroup.memory.memsw.limit_in_bytes > > and I can prove that it's working by writing a program to malloc memory > and watch the oom killer in operation when it reached the limit.. However > the output of 'top' still shows the entire memory of the host... > > Is this something fixable, or "just the way it is" for now?
Ah, just done more searching, (emails from Jan. this year), so forget this for now - seems it's "just the way is is" for now, but patches from http://www.tinola.com/lxc/ may be promising... Cheers, Gordon ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Lxc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lxc-users
