From: Libo Chen <libo.chen@oracle.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: mgorman@techsingularity.net, linux-kernel@vger.kernel.org,
mingo@redhat.com, tj@kernel.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, akpm@linux-foundation.org,
longman@redhat.com, lorenzo.stoakes@oracle.com
Subject: Re: [PATCH] sched/numa: skip VMA scanning on memory pinned to one NUMA node via cpuset.mems
Date: Wed, 12 Mar 2025 16:49:47 -0700 [thread overview]
Message-ID: <cde7af54-5481-499e-8a42-0111f555f2b1@oracle.com> (raw)
In-Reply-To: <20250312080102.GF19424@noisy.programming.kicks-ass.net>
On 3/12/25 01:01, Peter Zijlstra wrote:
> On Tue, Mar 11, 2025 at 09:04:47AM -0700, Libo Chen wrote:
>> When the memory of the current task is pinned to one NUMA node by cgroup,
>> there is no point in continuing the rest of VMA scanning and hinting page
>> faults as they will just be overhead. With this change, there will be no
>> more unnecessary PTE updates or page faults in this scenario.
> Its been a while since I looked at all this, but if we don't scan these
> pages, then it will not account for these pages, and the pinned memory
> will not become an attractor for the tasks that use this memory, right?
Hi Peter,
Yes, you are absolutely right. It will skip change_prot_numa() which
marks an
VMA to be inaccessible (not PROT_NONE though) by setting MM_CP_PROT_NUMA
flag,
without that there will be no numa faults on those pages, hence no task
migrations
towards those pages. But that's how similar cases are handled such as
hugetlb or
MPOL_BIND pages. If you look at the checks !vma_migratable() ||
!vma_policy_mof(),
etc, the rest of the loop will skipped if one of those is true. I am not
sure why
it's handle that way, maybe there are some old discussions I am not
aware of, I
personally think task migrations should be allowed even if the pages aren't.
Consider in most cases if cpuset.mems is set to one node, the same node
assuming
it's not a memory-only node is probably set in cpuset.cpus as well. I
think I can
add an additional check on CPU affinity, probably needs to add an helper
cpumask_to_nodemask(), so something like below?
+ cpumask_to_nodemask(¤t->cpus_mask, &allow_cpu_nodes);
+ if (nodes_weight(cpuset_current_mems_allowed) == 1 && nodes_weight(allow_cpu_nodes) == 1)
+ return;
Libo
>> Signed-off-by: Libo Chen <libo.chen@oracle.com>
>> ---
>> kernel/sched/fair.c | 7 +++++++
>> 1 file changed, 7 insertions(+)
>>
>> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
>> index c798d27952431..ec4749a7be33a 100644
>> --- a/kernel/sched/fair.c
>> +++ b/kernel/sched/fair.c
>> @@ -3315,6 +3315,13 @@ static void task_numa_work(struct callback_head *work)
>> if (p->flags & PF_EXITING)
>> return;
>>
>> + /*
>> + * Memory is pinned to only one NUMA node via cpuset.mems, naturally
>> + * no page can be migrated.
>> + */
>> + if (nodes_weight(cpuset_current_mems_allowed) == 1)
>> + return;
>> +
>> if (!mm->numa_next_scan) {
>> mm->numa_next_scan = now +
>> msecs_to_jiffies(sysctl_numa_balancing_scan_delay);
>> --
>> 2.43.5
>>
prev parent reply other threads:[~2025-03-12 23:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 16:04 Libo Chen
2025-03-11 17:42 ` Waiman Long
2025-03-12 2:18 ` Libo Chen
2025-03-12 8:01 ` Peter Zijlstra
2025-03-12 23:49 ` Libo Chen [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=cde7af54-5481-499e-8a42-0111f555f2b1@oracle.com \
--to=libo.chen@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=lorenzo.stoakes@oracle.com \
--cc=mgorman@techsingularity.net \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tj@kernel.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
all inboxes | Powered by JetHome®