On Wed, 25 Feb 2015, Christoph Lameter wrote: > On Wed, 25 Feb 2015, David Rientjes wrote: > > > NOTE: this is not about __GFP_THISNODE, this is only about GFP_THISNODE. > > Well but then its not removing it. You are replacing it with an inline > function. > Removing GFP_THISNODE, not __GFP_THISNODE. GFP_THISNODE, as the commit message says, is a special collection of flags that means "never try reclaim" and people confuse it for __GFP_THISNODE. There are legitimate usecases where we want __GFP_THISNODE, in other words restricting the allocation to only a specific node, and try reclaim but not warn in failure or retry. The most notable example is in the followup patch for thp, both for page faults and khugepaged, where we want to target the local node but silently fallback to small pages instead. This removes the special "no reclaim" behavior of __GFP_THISNODE | __GFP_NORETRY | __GFP_NOWARN and relies on clearing __GFP_WAIT instead. -- 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>