v1
2026-10-30
简化DAX vmemmap优化 · v1
移除 device DAX 专用 vmemmap_can_optimize 辅助,将优化可行性判断统一到 mem_section 与架构填充路径。
原始补丁链接
子 Patch(4)
1/4
powerpc/mm: make vmemmap_populate_compound_pages() static
vmemmap_populate_compound_pages() 已无外部使用者,改为 static,并从唯一调用点删除未使用的 dev_pagemap 参数,简化 PowerPC radix 页表代码。
2/4
powerpc/mm: drop powerpc vmemmap_can_optimize()
PowerPC no longer needs an architecture-specific vmemmap_can_optimize() override for DAX vmemmap optimization. Whether the optimized mapping can be used is now decided in the architecture-specific vm
3/4
mm/sparse-vmemmap: drop vmemmap_can_optimize()
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,
4/4
mm/sparse-vmemmap: drop @pgmap from vmemmap population APIs
The vmemmap population and memory hotplug paths no longer need @pgmap to decide whether a mapping can be optimized. That state is now carried in mem_section, and the architecture-specific population c