lkml.org 
[lkml]   [2013]   [Nov]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [patch] mm: memcg: do not declare OOM from __GFP_NOFAIL allocations
On Wed, 27 Nov 2013, Johannes Weiner wrote:

> > Ah, this is because of 3168ecbe1c04 ("mm: memcg: use proper memcg in limit
> > bypass") which just bypasses all of these allocations and charges the root
> > memcg. So if allocations want to bypass memcg isolation they just have to
> > be __GFP_NOFAIL?
>
> I don't think we have another option.
>

We don't give __GFP_NOFAIL allocations access to memory reserves in the
page allocator and we do call the oom killer for them so that a process is
killed so that memory is freed. Why do we have a different policy for
memcg?


\
 
 \ /
  Last update: 2013-11-27 23:01    [W:0.172 / U:0.020 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site