On 20.12.21 20:34, Hari Bathini wrote:
Commit 072355c1cf2d ("mm/cma: expose all pages to the buddy if
activation of an area fails") started exposing all pages to buddy
allocator on CMA activation failure. But there can be CMA users that
want to handle the reserved memory differently on CMA allocation
failure. Provide an option to opt out from exposing pages to buddy
for such cases.
Can you elaborate why that is important and what the target user can
actually do with it?
It certainly cannot do CMA allocations :)
--
Thanks,
David / dhildenb