[lkml]   [2020]   [Apr]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch] mm, oom: stop reclaiming if GFP_ATOMIC will start failing soon
On 2020/04/27 12:12, David Rientjes wrote:
> Tetsuo: the specific allocation that triggers a page allocation failure is
> not interesting; we have tens of thousands of examples. Each example is
> simply the unlucky last GFP_ATOMIC allocation that fails; the interesting
> point is the amount of free memory. In other words, when free memory is
> below ALLOC_HIGH watermarks, we assume that we have depleted memory
> reserves *faster* than when user allocations started to fail. In the
> interest of userspace being responsive, we should oom kill here.

My interest is, which function (and which process if process context) is [ab]using
GFP_ATOMIC (or __GFP_MEMALLOC) allocations enough to hit memory allocation failure.
GFP_NOWAIT (or __GFP_NOMEMALLOC) could be used if that allocation can't sleep and
can't shortly recover free memory.

 \ /
  Last update: 2020-04-27 07:04    [W:0.169 / U:0.492 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site