mm: Always split CMA pages
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 <e7b4910f4742918f5926c991d8a2cd122ac7e295@codeaurora.org>
Signed-off-by: Stephen Boyd <010521127f513270fe503d86ab8316ac5147f4b7@codeaurora.org>

TeamVee-Kanas/android_kernel_samsung_kanas,TeamVee-Kanas/android_kernel_samsung_kanas,TeamVee-Kanas/android_kernel_samsung_kanas,TeamVee-Kanas/android_kernel_samsung_kanas,TeamVee-Kanas/android_kernel_samsung_kanas