I'm from the Open Grid Scheduler Project (the official open source Grid Engine maintainer in the post Sun world), and we are using cgroups as the job container in our scheduler.
Since LXC also uses cgroups, I was wondering if the developers want to change the behavior of "memory.memsw.limit_in_bytes" of the memory controller? With the "memory.memsw.limit_in_bytes" limit set, when the processes in the cgroup exceed the memory usage, then the OOM killer would pick a process and kill it. What we want is the setrlimit() behavior, which actually sets the upper bound of the process' data segment size, and thus sbrk & malloc would get error instead. See Grid Engine cgroups Integration: http://blogs.scalablelogic.com/2012/05/grid-engine-cgroups-integration.html If LXC is not using setting the "memory.memsw.limit_in_bytes" limit, then may be it is not a real concern... Rayson ================================ Open Grid Scheduler / Grid Engine http://gridscheduler.sourceforge.net/ Scalable Grid Engine Support Program http://www.scalablelogic.com/ ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
