On Wed, 27 Nov 2013, Johannes Weiner wrote: > > 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? > > Oh boy, that's the epic story we dealt with all throughout the last > merge window... ;-) > > __GFP_NOFAIL allocations might come in with various filesystem locks > held that could prevent an OOM victim from exiting, so a loop around > the OOM killer in an allocation context is prone to loop endlessly. > Ok, so let's forget about GFP_KERNEL | __GFP_NOFAIL since anything doing __GFP_FS should not be holding such locks, we have some of those in the drivers code and that makes sense that they are doing GFP_KERNEL. Focusing on the GFP_NOFS | __GFP_NOFAIL allocations in the filesystem code, the kernel oom killer independent of memcg never gets called because !__GFP_FS and they'll simply loop around the page allocator forever. In the past, Andrew has expressed the desire to get rid of __GFP_NOFAIL entirely since it's flawed when combined with GFP_NOFS (and GFP_KERNEL | __GFP_NOFAIL could simply be reimplemented in the caller) because of the reason you point out in addition to making it very difficult in the page allocator to free memory independent of memcg. So I'm wondering if we should just disable the oom killer in memcg for __GFP_NOFAIL as you've done here, but not bypass to the root memcg and just allow them to spin? I think we should be focused on the fixing the callers rather than breaking memcg isolation. -- 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>