Re: [PATCH v5 0/6] Introduce ZONE_CMA
From: Aneesh Kumar K.V <hidden>
Date: 2016-08-30 10:39:51
Also in:
lkml
Joonsoo Kim [off-list ref] writes:
2016-08-29 18:27 GMT+09:00 Aneesh Kumar K.V [off-list ref]:quoted
js1304@gmail.com writes:quoted
From: Joonsoo Kim <redacted> Hello, Changes from v4 o Rebase on next-20160825 o Add general fix patch for lowmem reserve o Fix lowmem reserve ratio o Fix zone span optimizaion per Vlastimil o Fix pageset initialization o Change invocation timing on cma_init_reserved_areas()I don't see much information regarding how we interleave between ZONE_CMA and other zones for movable allocation. Is that explained in any of the patch ? The fair zone allocator got removed by e6cbd7f2efb433d717af72aa8510a9db6f7a7e05Interleaving would not work since the fair zone allocator policy is removed. I don't think that it's a big problem because it is just matter of timing to fill up the memory. Eventually, memory on ZONE_CMA will be fully used in any case.
Does that mean a CMA allocation will now be slower because in most case we will need to reclaim ? The zone list will now have ZONE_CMA in the beginning right ? -aneesh -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>