On 08/24/2015 02:09 PM, Mel Gorman wrote:
The first key hazard to watch out for is callers that removed __GFP_WAIT and was depending on access to atomic reserves for inconspicuous reasons. In some cases it may be appropriate for them to use __GFP_HIGH.
Hm so I think this hazard should be expanded. If such caller comes from interrupt and doesn't use __GFP_ATOMIC, the ALLOC_CPUSET with restrictions taken from the interrupted process will also apply to him?
-- 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>