From: Waiman Long <llong@redhat.com>
To: Libo Chen <libo.chen@oracle.com>,
peterz@infradead.org, mgorman@techsingularity.net
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com, tj@kernel.org,
juri.lelli@redhat.com, vincent.guittot@linaro.org,
akpm@linux-foundation.org, lorenzo.stoakes@oracle.com
Subject: Re: [PATCH] sched/numa: skip VMA scanning on memory pinned to one NUMA node via cpuset.mems
Date: Tue, 11 Mar 2025 13:42:53 -0400 [thread overview]
Message-ID: <825fb8bc-91ca-4de4-9c8d-44590b6c1cba@redhat.com> (raw)
In-Reply-To: <20250311160447.2813222-1-libo.chen@oracle.com>
On 3/11/25 12:04 PM, 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.
>
> 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);
Do you have any performance improvement data that can be included in the
commit log?
Cheers,
Longman
next prev parent reply other threads:[~2025-03-11 17:42 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 [this message]
2025-03-12 2:18 ` Libo Chen
2025-03-12 8:01 ` Peter Zijlstra
2025-03-12 23:49 ` Libo Chen
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=825fb8bc-91ca-4de4-9c8d-44590b6c1cba@redhat.com \
--to=llong@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=juri.lelli@redhat.com \
--cc=libo.chen@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--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®