[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <daaf50aa-896b-4dc3-891c-6595b73f271f@amd.com>
Date: Thu, 22 May 2025 10:12:03 +0530
From: Bharata B Rao <bharata@....com>
To: Zi Yan <ziy@...dia.com>
Cc: Donet Tom <donettom@...ux.ibm.com>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, Jonathan.Cameron@...wei.com, dave.hansen@...el.com,
gourry@...rry.net, hannes@...xchg.org, mgorman@...hsingularity.net,
mingo@...hat.com, peterz@...radead.org, raghavendra.kt@....com,
riel@...riel.com, rientjes@...gle.com, sj@...nel.org, weixugc@...gle.com,
willy@...radead.org, ying.huang@...ux.alibaba.com, dave@...olabs.net,
nifan.cxl@...il.com, joshua.hahnjy@...il.com, xuezhengchu@...wei.com,
yiannis@...corp.com, akpm@...ux-foundation.org, david@...hat.com
Subject: Re: [RFC PATCH v0 2/2] mm: sched: Batch-migrate misplaced pages
On 22-May-25 12:10 AM, Zi Yan wrote:
> On 21 May 2025, at 14:25, Donet Tom wrote:
>
> In memory tiering mode, folio_last_cpupid() gives page access time
> for slow memory folios. In !folio_use_access_time() case,
> folio_last_cpupid() gives last cpupid. Now it is reused for node
> id. It is too confusing. At least, a new function like folio_get_target_nid()
> should be added to return a nid only if folio is isolated.
Yes, it can be confusing. If this approach of using last_cpupid field to
store the target_nid is found to be feasible, I will cleanup the names
as you suggest.
Regards,
Bharata.
Powered by blists - more mailing lists