Re: [PATCH v3 4/5] mm/sparse-vmemmap: drop vmemmap_can_optimize()
From: Lance Yang
Date: Mon Nov 09 2026 - 00:50:22 EST
On Sat, Nov 07, 2026 at 12:31:21PM +0800, Muchun Song wrote:
>section_vmemmap_optimizable() can already decide whether a section uses
>vmemmap optimization based on the section compound order. The DAX-specific
>vmemmap_can_optimize() helper duplicates that policy, so remove it to
>simplify the code.
>
>Signed-off-by: Muchun Song <songmuchun@xxxxxxxxxxxxx>
>---
With the arch fallbacks handled by the previous patches, we can just drop
vmemmap_can_optimize() now ;)
Nothing jumped out at me, so:
Reviewed-by: Lance Yang <lance.yang@xxxxxxxxx>