[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250506184155.587070-1-nifan.cxl@gmail.com>
Date: Tue, 6 May 2025 11:38:28 -0700
From: nifan.cxl@...il.com
To: muchun.song@...ux.dev,
willy@...radead.org,
osalvador@...e.de
Cc: mcgrof@...nel.org,
a.manzanares@...sung.com,
dave@...olabs.net,
akpm@...ux-foundation.org,
david@...hat.com,
linux-mm@...ck.org,
linux-kernel@...r.kernel.org,
nifan.cxl@...il.com,
Fan Ni <fan.ni@...sung.com>
Subject: [RFC 0/1] Convert is_migrate_isolate_page() to is_migrate_isolate_folio()
From: Fan Ni <fan.ni@...sung.com>
Sending out this patch per Matthew Wilcox's suggestion
that we need to convert is_migrate_isolate_page() to use folio
https://lore.kernel.org/linux-mm/Z_XmUrbxKtYmzmJ6@casper.infradead.org/
However, when looking into the code, I have noticed that among the uers
of is_migrate_isolate_page(), in most cases the page passed in is from a
a pageblock.
I am not sure how we should proceed with these cases.
Should we deal with pageblock or just leave it as it is and only do the page
to folio conversion for the pages within?
So This RFC is mainly sent for collecting input about how to move forward.
Fan Ni (1):
mm: Convert is_migrate_isolate_page() to is_migrate_isolate_folio()
include/linux/page-isolation.h | 6 +++---
mm/hugetlb.c | 2 +-
mm/page_isolation.c | 10 +++++-----
3 files changed, 9 insertions(+), 9 deletions(-)
--
2.47.2
Powered by blists - more mailing lists