From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Donet Tom <donettom@linux.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: Ritesh Harjani <ritesh.list@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Ying Huang <huang.ying.caritas@gmail.com>,
Juri Lelli <juri.lelli@redhat.com>, Mel Gorman <mgorman@suse.de>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] sched/numa, mm: Skip page promotion if cpu pid is valid
Date: Thu, 26 Mar 2026 11:29:49 +0100 [thread overview]
Message-ID: <f41ab7cb-4430-4338-8812-eb6aa98e9bf9@kernel.org> (raw)
In-Reply-To: <20260326071216.11883-1-donettom@linux.ibm.com>
On 3/26/26 08:12, Donet Tom wrote:
> If memory tiering is disabled, cpupid of slow memory pages may
> contain a valid CPU and PID. If tiering is enabled at runtime,
> there is a chance that in should_numa_migrate_memory(), this
> valid CPU/PID is treated as a last access timestamp, leading
> to unnecessary promotion.
Is that measurable? Should we at least have a Fixes: ?
>
> Prevent this by skipping promotion when cpupid is valid.
>
> Signed-off-by: Donet Tom <donettom@linux.ibm.com>
> ---
> kernel/sched/fair.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index 4b43809a3fb1..f5830a5a94d5 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -2001,6 +2001,13 @@ bool should_numa_migrate_memory(struct task_struct *p, struct folio *folio,
> unsigned int latency, th, def_th;
> long nr = folio_nr_pages(folio);
>
/*
* When ...
> + /* When tiering is enabled at runtime, last_cpupid may
> + * hold a valid cpupid instead of an access timestamp.
> + * If so, skip page promotion.
> + */
> + if (cpupid_valid(folio_last_cpupid(folio)))
> + return false;
> +
IIUC, as timestamp we use jiffies_to_msecs(). So, soon after bootup,
we would no longer get false positives for cpupid_valid().
I suppose overflows are not a problem, correct?
So what we're saying is that folio_use_access_time()==true does not
imply that there is actually a valid time in there.
In numa_migrate_check() we could still use the valid cpuid I guess and
make that code a bit clearer?
diff --git a/mm/memory.c b/mm/memory.c
index 631205a384e1..ba68933a9e4a 100644
--- a/mm/memory.c
+++ b/mm/memory.c
@@ -6119,10 +6119,9 @@ int numa_migrate_check(struct folio *folio, struct vm_fault *vmf,
* For memory tiering mode, cpupid of slow memory page is used
* to record page access time. So use default value.
*/
- if (folio_use_access_time(folio))
+ *last_cpupid = folio_last_cpupid(folio);
+ if (!cpupid_valid(*last_cpupid))
*last_cpupid = (-1 & LAST_CPUPID_MASK);
- else
- *last_cpupid = folio_last_cpupid(folio);
/* Record the current PID accessing VMA */
vma_set_access_pid_bit(vma);
The change itself here looks reasonable to me.
Acked-by: David Hildenbrand (Arm) <david@kernel.org>
--
Cheers,
David
prev parent reply other threads:[~2026-03-26 10:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 7:12 [PATCH] sched/numa, mm: Skip page promotion if cpu pid is valid Donet Tom
2026-03-26 10:29 ` David Hildenbrand (Arm) [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f41ab7cb-4430-4338-8812-eb6aa98e9bf9@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=dietmar.eggemann@arm.com \
--cc=donettom@linux.ibm.com \
--cc=huang.ying.caritas@gmail.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=ritesh.list@gmail.com \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox