On Wed 11-11-15 10:54:46, Johannes Weiner wrote: > On Wed, Nov 11, 2015 at 02:48:17PM +0100, mho...@kernel.org wrote: > > From: Michal Hocko <mho...@suse.com> > > > > __GFP_NOFAIL is a big hammer used to ensure that the allocation > > request can never fail. This is a strong requirement and as such > > it also deserves a special treatment when the system is OOM. The > > primary problem here is that the allocation request might have > > come with some locks held and the oom victim might be blocked > > on the same locks. This is basically an OOM deadlock situation. > > > > This patch tries to reduce the risk of such a deadlocks by giving > > __GFP_NOFAIL allocations a special treatment and let them dive into > > memory reserves after oom killer invocation. This should help them > > to make a progress and release resources they are holding. The OOM > > victim should compensate for the reserves consumption. > > > > Signed-off-by: Michal Hocko <mho...@suse.com> > > --- > > > > Hi, > > this has been posted previously as a part of larger GFP_NOFS related > > patch set > > (http://lkml.kernel.org/r/1438768284-30927-1-git-send-email-mhocko%40kernel.org) > > but Andrea was asking basically the same thing at LSF early this year > > (I cannot seem to find it in any public archive though). I think the > > patch makes some sense on its own. > > I sent this right after LSF based on Andrea's suggestion: > > https://lkml.org/lkml/2015/3/25/37
Ohh, I completely forgot as it was part of a larger series. Thanks for the pointer. -- Michal Hocko SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
