Re: [PATCH v3 3/3] oom: decouple mems_allowed from oom_unkillable_task

2019-06-27 Thread Shakeel Butt
On Tue, Jun 25, 2019 at 11:55 PM Michal Hocko wrote: > > On Mon 24-06-19 14:26:31, Shakeel Butt wrote: > > The commit ef08e3b4981a ("[PATCH] cpusets: confine oom_killer to > > mem_exclusive cpuset") introduces a heuristic where a potential > > oom-killer victim is skipped if the intersection of th

Re: [PATCH v3 3/3] oom: decouple mems_allowed from oom_unkillable_task

2019-06-26 Thread Roman Gushchin
On Mon, Jun 24, 2019 at 02:26:31PM -0700, Shakeel Butt wrote: > The commit ef08e3b4981a ("[PATCH] cpusets: confine oom_killer to > mem_exclusive cpuset") introduces a heuristic where a potential > oom-killer victim is skipped if the intersection of the potential victim > and the current (the proces

Re: [PATCH v3 3/3] oom: decouple mems_allowed from oom_unkillable_task

2019-06-26 Thread Michal Hocko
On Wed 26-06-19 17:12:10, Hillf Danton wrote: > > On Mon, 24 Jun 2019 14:27:11 -0700 (PDT) Shakeel Butt wrote: > > > > @@ -1085,7 +1091,8 @@ bool out_of_memory(struct oom_control *oc) > > check_panic_on_oom(oc, constraint); > > > > if (!is_memcg_oom(oc) && sysctl_oom_kill_allocating_tas

Re: [PATCH v3 3/3] oom: decouple mems_allowed from oom_unkillable_task

2019-06-25 Thread Michal Hocko
On Mon 24-06-19 14:26:31, Shakeel Butt wrote: > The commit ef08e3b4981a ("[PATCH] cpusets: confine oom_killer to > mem_exclusive cpuset") introduces a heuristic where a potential > oom-killer victim is skipped if the intersection of the potential victim > and the current (the process triggered the

[PATCH v3 3/3] oom: decouple mems_allowed from oom_unkillable_task

2019-06-24 Thread Shakeel Butt
The commit ef08e3b4981a ("[PATCH] cpusets: confine oom_killer to mem_exclusive cpuset") introduces a heuristic where a potential oom-killer victim is skipped if the intersection of the potential victim and the current (the process triggered the oom) is empty based on the reason that killing such vi