Messages in this thread | | | Date | Wed, 11 Jan 2023 15:12:46 +0100 | Subject | Re: [PATCH 6/7] mm/page_alloc: Give GFP_ATOMIC and non-blocking allocations access to reserves | From | Vlastimil Babka <> |
| |
On 1/9/23 16:16, Mel Gorman wrote: > Explicit GFP_ATOMIC allocations get flagged ALLOC_HARDER which is a bit > vague. In preparation for removing __GFP_ATOMIC, give GFP_ATOMIC and > other non-blocking allocation requests equal access to reserve. Rename > ALLOC_HARDER to ALLOC_NON_BLOCK to make it more clear what the flag > means. > > Signed-off-by: Mel Gorman <mgorman@techsingularity.net>
Acked-by: Vlastimil Babka <vbabka@suse.cz>
| |