Messages in this thread | | | Date | Wed, 27 Nov 2013 13:38:59 -0800 (PST) | From | David Rientjes <> | Subject | Re: [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?
| |