[lkml]   [2013]   [Nov]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch] mm, vmscan: abort futile reclaim if we've been oom killed
On Mon, 18 Nov 2013, Johannes Weiner wrote:

> > Um, no, those processes are going through a repeated loop of direct
> > reclaim, calling the oom killer, iterating the tasklist, finding an
> > existing oom killed process that has yet to exit, and looping. They
> > wouldn't loop for too long if we can reduce the amount of time that it
> > takes for that oom killed process to exit.
> I'm not talking about the big loop in the page allocator. The victim
> is going through the same loop. This patch is about the victim being
> in a pointless direct reclaim cycle when it could be exiting, all I'm
> saying is that the other tasks doing direct reclaim at that moment
> should also be quitting and retrying the allocation.

"All other tasks" would be defined as though sharing the same mempolicy
context as the oom kill victim or the same set of cpuset mems, I'm not
sure what type of method for determining reclaim eligiblity you're
proposing to avoid pointlessly spinning without making progress. Until an
alternative exists, my patch avoids the needless spinning and expedites
the exit, so I'll ask that it be merged.

 \ /
  Last update: 2013-11-19 02:41    [W:0.077 / U:1.288 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site