[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250609200048.50914-1-sj@kernel.org>
Date: Mon, 9 Jun 2025 13:00:45 -0700
From: SeongJae Park <sj@...nel.org>
To:
Cc: SeongJae Park <sj@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
David Hildenbrand <david@...hat.com>,
Honggyu Kim <honggyu.kim@...com>,
Johannes Weiner <hannes@...xchg.org>,
Lorenzo Stoakes <lorenzo.stoakes@...cle.com>,
Michal Hocko <mhocko@...nel.org>,
Qi Zheng <zhengqi.arch@...edance.com>,
Shakeel Butt <shakeel.butt@...ux.dev>,
Simon Wang <wangchuanguo@...pur.com>,
damon@...ts.linux.dev,
kernel-team@...a.com,
linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Subject: [RFC PATCH 0/3] mm/damon: use alloc_migration_target() for DAMOS_MIGRATE_{HOT,COLD}
DAMOS_MIGRATE_{HOT,COLD} implementation resembles that for demotion, and
hence the behavior is also similar to that. But, since those are not
only for demotion but general migrations, it would be better to match
with that for move_pages() system call. Make the implementation and the
behavior more similar to move_pages() by not setting migration fallback
nodes, and using alloc_migration_target() instead of
alloc_migrate_folio().
alloc_migrate_folio() was renamed from alloc_demote_folio() and been
non-static function, to let DAMOS_MIGRATE_{HOT,COLD} call it. As
alloc_migration_target() is called instead, the renaming and non-static
changes are no more required but could only make future code readers
be confused. Revert the changes, too.
SeongJae Park (3):
mm/damon/paddr: use alloc_migartion_target() with no migration
fallback nodemask
Revert "mm: rename alloc_demote_folio to alloc_migrate_folio"
Revert "mm: make alloc_demote_folio externally invokable for
migration"
mm/damon/paddr.c | 4 +---
mm/internal.h | 1 -
mm/vmscan.c | 5 +++--
3 files changed, 4 insertions(+), 6 deletions(-)
base-commit: 7af1516cc219fe5ecc2e2ba01e578a75e955d0b4
--
2.39.5
Powered by blists - more mailing lists