mm: Always split CMA pages
The page allocator (correctly) checks watermarks when determining if a page should be split to avoid fragmentation. For general migration, this is acceptable but this may lead to high rates of CMA failure under memory pressure. Since CMA migration failures have a very high cost from a user perspective, skip the watermark checks and always split the page. This may result in more fragmentation in the zone, but it's worth it given the benefit to CMA allocations. Signed-off-by:Laura Abbott <lauraa@codeaurora.org> Signed-off-by:
Stephen Boyd <sboyd@codeaurora.org>
Loading
Please register or sign in to comment