From: Aaron Tomlin <atomlin@atomlin.com>
To: oleg@redhat.com, akpm@linux-foundation.org,
gregkh@linuxfoundation.org, david@kernel.org, brauner@kernel.org,
mingo@kernel.org
Cc: sean@ashe.io, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: [v2 PATCH 0/1] fs/proc: Expose mm_cpumask in /proc/[pid]/status
Date: Fri, 26 Dec 2025 16:14:06 -0500 [thread overview]
Message-ID: <20251226211407.2252573-1-atomlin@atomlin.com> (raw)
Hi Oleg, David, Greg, Andrew,
This patch introduces two new fields to /proc/[pid]/status to display the
set of CPUs, representing the CPU affinity of the process's active memory
context, in both mask and list format: "Cpus_active_mm" and
"Cpus_active_mm_list". The mm_cpumask is primarily used for TLB and cache
synchronisation.
Exposing this information allows userspace to easily describe the
relationship between CPUs where a memory descriptor is "active" and the
CPUs where the thread is allowed to execute. The primary intent is to
provide visibility into the "memory footprint" across CPUs, which is
invaluable for debugging performance issues related to IPI storms and TLB
shootdowns in large-scale NUMA systems. The CPU-affinity sets the boundary;
the mm_cpumask records the arrival; they complement each other.
Frequent mm_cpumask changes may indicate instability in placement policies
or excessive task migration overhead.
Changes since v1:
- Document new Cpus_active_mm and Cpus_active_mm_list entries in
/proc/[pid]/status (Oleg Nesterov)
[1]: https://lore.kernel.org/lkml/20251217024603.1846651-1-atomlin@atomlin.com/
Aaron Tomlin (1):
fs/proc: Expose mm_cpumask in /proc/[pid]/status
Documentation/filesystems/proc.rst | 3 +++
fs/proc/array.c | 22 +++++++++++++++++++++-
2 files changed, 24 insertions(+), 1 deletion(-)
--
2.51.0
next reply other threads:[~2025-12-26 21:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-26 21:14 Aaron Tomlin [this message]
2025-12-26 21:14 ` [v2 PATCH 1/1] " Aaron Tomlin
2025-12-30 21:16 ` David Hildenbrand (Red Hat)
2026-01-01 1:19 ` Aaron Tomlin
2026-01-06 18:54 ` David Hildenbrand (Red Hat)
2026-01-15 18:40 ` Aaron Tomlin
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=20251226211407.2252573-1-atomlin@atomlin.com \
--to=atomlin@atomlin.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=david@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=sean@ashe.io \
/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
Powered by JetHome