On 08/24/2017 08:36 AM, js1304@xxxxxxxxx wrote: > From: Joonsoo Kim <iamjoonsoo.kim@xxxxxxx> > > 0. History > > This patchset is the follow-up of the discussion about the > "Introduce ZONE_CMA (v7)" [1]. Please reference it if more information > is needed. > [...] > > [1]: lkml.kernel.org/r/1491880640-9944-1-git-send-email-iamjoonsoo.kim@xxxxxxx > [2]: https://lkml.org/lkml/2014/10/15/623 > [3]: http://www.spinics.net/lists/linux-mm/msg100562.html > > Reviewed-by: Aneesh Kumar K.V <aneesh.kumar@xxxxxxxxxxxxxxxxxx> > Acked-by: Vlastimil Babka <vbabka@xxxxxxx> The previous version has introduced ZONE_CMA, so I would think switching to ZONE_MOVABLE is enough to drop previous reviews. Perhaps most of the code involved is basically the same, though? Anyway I checked the current patch and did some basic tests with qemu, so you can keep my ack. BTW, if we dropped NR_FREE_CMA_PAGES, could we also drop MIGRATE_CMA and related hooks? Is that counter really that useful as it works right now? It will decrease both by CMA allocations (which has to be explicitly freed) and by movable allocations (which can be migrated). What if only CMA alloc/release touched it? -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>
