Re: [patch -mm 3/4] mm, memcg: replace memory.oom_group with policy tunable

Michal Hocko
2018-01-23T15:53:01Z

On Mon 22-01-18 14:34:39, David Rientjes wrote:
> On Sat, 20 Jan 2018, Tejun Heo wrote:
[...]
> > I don't see any blocker here. The issue you're raising can and should
> > be handled separately.
> >
>
> It can't, because the current patchset locks the system into a single
> selection criteria that is unnecessary and the mount option would become a
> no-op after the policy per subtree becomes configurable by the user as
> part of the hierarchy itself.

This is simply not true! OOM victim selection has changed in the
past and will be always a subject to changes in future. Current
implementation doesn't provide any externally controlable selection
policy and therefore the default can be assumed. Whatever that default
means now or in future. The only contract added here is the kill full
memcg if selected and that can be implemented on _any_ selection policy.

--
Michal Hocko
SUSE Labs