On Thu 18-05-17 17:28:04, Roman Gushchin wrote: > Traditionally, the OOM killer is operating on a process level. > Under oom conditions, it finds a process with the highest oom score > and kills it. > > This behavior doesn't suit well the system with many running > containers. There are two main issues: > > 1) There is no fairness between containers. A small container with > a few large processes will be chosen over a large one with huge > number of small processes. > > 2) Containers often do not expect that some random process inside > will be killed. So, in general, a much safer behavior is > to kill the whole cgroup. Traditionally, this was implemented > in userspace, but doing it in the kernel has some advantages, > especially in a case of a system-wide OOM. > > To address these issues, cgroup-aware OOM killer is introduced. > Under OOM conditions, it looks for a memcg with highest oom score, > and kills all processes inside. > > Memcg oom score is calculated as a size of active and inactive > anon LRU lists, unevictable LRU list and swap size. > > For a cgroup-wide OOM, only cgroups belonging to the subtree of > the OOMing cgroup are considered. While this might make sense for some workloads/setups it is not a generally acceptable policy IMHO. We have discussed that different OOM policies might be interesting few years back at LSFMM but there was no real consensus on how to do that. One possibility was to allow bpf like mechanisms. Could you explore that path? -- Michal Hocko SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
