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 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/
