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?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>