[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250424000146.1197285-1-libo.chen@oracle.com>
Date: Wed, 23 Apr 2025 17:01:44 -0700
From: Libo Chen <libo.chen@...cle.com>
To: akpm@...ux-foundation.org, rostedt@...dmis.org, peterz@...radead.org,
mgorman@...e.de, mingo@...hat.com, juri.lelli@...hat.com,
vincent.guittot@...aro.org, tj@...nel.org, llong@...hat.com
Cc: sraithal@....com, venkat88@...ux.ibm.com, kprateek.nayak@....com,
raghavendra.kt@....com, yu.c.chen@...el.com, tim.c.chen@...el.com,
vineethr@...ux.ibm.com, chris.hyser@...cle.com,
daniel.m.jordan@...cle.com, lorenzo.stoakes@...cle.com,
mkoutny@...e.com, linux-mm@...ck.org, cgroups@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: [PATCH v4 0/2] sched/numa: Skip VMA scanning on memory pinned to one NUMA node via cpuset.mem
v1->v2:
1. add perf improvment numbers in commit log. Yet to find perf diff on
will-it-scale, so not included here. Plan to run more workloads.
2. add tracepoint.
3. To peterz's comment, this will make it impossible to attract tasks to
those memory just like other VMA skippings. This is the current
implementation, I think we can improve that in the future, but at the
moment it's probabaly better to keep it consistent.
v2->v3:
1. add enable_cpuset() based on Mel's suggestion but again I think it's
redundant
2. print out nodemask with %*p.. format in the tracepoint
v3->v4:
1. fix an unsafe dereference of a pointer to content not on ring buffer,
namely mem_allowed_ptr in the tracepoint.
Libo Chen (2):
sched/numa: Skip VMA scanning on memory pinned to one NUMA node via
cpuset.mems
sched/numa: Add tracepoint that tracks the skipping of numa balancing
due to cpuset memory pinning
include/trace/events/sched.h | 31 +++++++++++++++++++++++++++++++
kernel/sched/fair.c | 9 +++++++++
2 files changed, 40 insertions(+)
--
2.43.5
Powered by blists - more mailing lists