Messages in this thread | ![/](/images/icornerl.gif) | | Date | Tue, 25 Oct 2011 23:16:55 -0700 | Subject | Re: [PATCH] mm: avoid livelock on !__GFP_FS allocations | From | Colin Cross <> |
| |
On Tue, Oct 25, 2011 at 11:12 PM, David Rientjes <rientjes@google.com> wrote: > On Tue, 25 Oct 2011, David Rientjes wrote: > >> Ok, so __GFP_NORETRY it is. Just make sure that when >> pm_restrict_gfp_mask() masks off __GFP_IO and __GFP_FS that it also sets >> __GFP_NORETRY even though the name of the function no longer seems >> appropriate anymore. >> > > Or, rather, when pm_restrict_gfp_mask() clears __GFP_IO and __GFP_FS that > it also has the same behavior as __GFP_NORETRY in should_alloc_retry() by > setting a variable in file scope. >
Why do you prefer that over adding a gfp_required_mask? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| ![\](/images/icornerr.gif) |