Leftovers found while fixing VSTOR-151607, where the allocator of memory.numa_migrate had fallen behind the upstream function it was copied from. Nothing here changes behaviour. Applies on top of "mm/memcontrol: numa_migrate destinations of the source folio order".
- 1: update_lru_sizes() lost its only caller when the isolation loop switched to lruvec_del_folio(); static __always_inline, so no warning ever came. - 2: the comment in the isolation loop told the rebase history of the code. It now names the upstream functions the loop and the allocator copy (isolate_migratepages_block(), isolate_lru_folios(), alloc_migration_target()), which is what the next rebase has to compare against. The commented-out conditions and the pre-folio name of the allocator go with it. - 3: the MAX_SCAN argument of memory.numa_migrate is documented in pages while the scan counts folios. https://virtuozzo.atlassian.net/browse/VSTOR-152197 Assisted-by: LLM Signed-off-by: Konstantin Khorenko <[email protected]> --- Konstantin Khorenko (3): mm/memcontrol: drop the unused update_lru_sizes() mm/memcontrol: say where the numa_migrate code comes from mm/memcontrol: memory.numa_migrate MAX_SCAN counts folios mm/memcontrol.c | 54 +++++++++++++----------------------------------------- 1 file changed, 13 insertions(+), 41 deletions(-) --- base-commit: 8f4b2db111bee113348656f1b1f98c841d7c19e7 change-id: 20261028-b4-prep-khorenko-vstor-152197-numa-migrate-cleanup-dcc488d8d106 Best regards, -- Konstantin Khorenko, Virtuozzo Linux Kernel Team _______________________________________________ Devel mailing list [email protected] https://lists.openvz.org/mailman/listinfo/devel
