Re: [PATCH 4/4] oom: split out forced OOM killer

2015-07-09 Thread David Rientjes
On Thu, 9 Jul 2015, Michal Hocko wrote: > > > The forced OOM killing is currently wired into out_of_memory() call > > > even though their objective is different which makes the code ugly > > > and harder to follow. Generic out_of_memory path has to deal with > > > configuration settings and heuris

Re: [PATCH 4/4] oom: split out forced OOM killer

2015-07-09 Thread Michal Hocko
On Wed 08-07-15 16:41:23, David Rientjes wrote: > On Wed, 8 Jul 2015, Michal Hocko wrote: > > > From: Michal Hocko > > > > The forced OOM killing is currently wired into out_of_memory() call > > even though their objective is different which makes the code ugly > > and harder to follow. Generic

Re: [PATCH 4/4] oom: split out forced OOM killer

2015-07-08 Thread David Rientjes
On Wed, 8 Jul 2015, Michal Hocko wrote: > From: Michal Hocko > > The forced OOM killing is currently wired into out_of_memory() call > even though their objective is different which makes the code ugly > and harder to follow. Generic out_of_memory path has to deal with > configuration settings a

[PATCH 4/4] oom: split out forced OOM killer

2015-07-08 Thread Michal Hocko
From: Michal Hocko The forced OOM killing is currently wired into out_of_memory() call even though their objective is different which makes the code ugly and harder to follow. Generic out_of_memory path has to deal with configuration settings and heuristics which are completely irrelevant to the