Harald Dunkel
2018-08-20 11:00:09 UTC
Hi folks,
AFAIU lxc.cgroup.memory.limit_in_bytes provides a limit for
physical memory allocation within the container (text + heap
+ stack). This is not reserved memory. The containers don't
have a private memory management. A container might run into
swap memory, even though it has not reached this limit yet.
Question is: How do I limit the RAM a container might use for
memory mapped IO and buffer cache? Do I have to worry about
"bad" containers using up all RAM here, leaving none for its
neighbors?
Every insightful comment is highly appreciated
Harri
AFAIU lxc.cgroup.memory.limit_in_bytes provides a limit for
physical memory allocation within the container (text + heap
+ stack). This is not reserved memory. The containers don't
have a private memory management. A container might run into
swap memory, even though it has not reached this limit yet.
Question is: How do I limit the RAM a container might use for
memory mapped IO and buffer cache? Do I have to worry about
"bad" containers using up all RAM here, leaving none for its
neighbors?
Every insightful comment is highly appreciated
Harri