From: Andrew Morton <akpm@linux-foundation.org>
To: "JP Kobryn (Meta)" <jp.kobryn@linux.dev>
Cc: linux-mm@kvack.org, vbabka@kernel.org, mhocko@suse.com,
ying.huang@linux.alibaba.com, hannes@cmpxchg.org,
shakeel.butt@linux.dev, gourry@gourry.net, kasong@tencent.com,
qi.zheng@linux.dev, baohua@kernel.org, axelrasmussen@google.com,
yuanchu@google.com, weixugc@google.com, david@kernel.org,
ljs@kernel.org, liam@infradead.org, rppt@kernel.org,
surenb@google.com, ziy@nvidia.com, matthew.brost@intel.com,
joshua.hahnjy@gmail.com, rakie.kim@sk.com, byungchul@sk.com,
apopple@nvidia.com, linux-kernel@vger.kernel.org,
kernel-team@meta.com
Subject: Re: [PATCH v4] mm/mempolicy: track user-defined mempolicy allocations
Date: Mon, 27 Apr 2026 14:11:23 -0700 [thread overview]
Message-ID: <20260427141123.734c66450100c0f900e02947@linux-foundation.org> (raw)
In-Reply-To: <20260427151520.137341-1-jp.kobryn@linux.dev>
On Mon, 27 Apr 2026 08:15:20 -0700 "JP Kobryn (Meta)" <jp.kobryn@linux.dev> wrote:
> When investigating pressure on a NUMA node, there is no straightforward way
> to determine which user-defined policies are driving allocations to it.
>
> Add NUMA mempolicy allocation counters as new node stat items. These
> counters track allocations to nodes and also whether the allocations were
> intentional or fallbacks.
AI review:
https://sashiko.dev/#/patchset/20260427151520.137341-1-jp.kobryn@linux.dev
next prev parent reply other threads:[~2026-04-27 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 15:15 [PATCH v4] mm/mempolicy: track user-defined mempolicy allocations JP Kobryn (Meta)
2026-04-27 21:11 ` Andrew Morton [this message]
2026-05-05 6:22 ` JP Kobryn (Meta)
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=20260427141123.734c66450100c0f900e02947@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=axelrasmussen@google.com \
--cc=baohua@kernel.org \
--cc=byungchul@sk.com \
--cc=david@kernel.org \
--cc=gourry@gourry.net \
--cc=hannes@cmpxchg.org \
--cc=joshua.hahnjy@gmail.com \
--cc=jp.kobryn@linux.dev \
--cc=kasong@tencent.com \
--cc=kernel-team@meta.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=matthew.brost@intel.com \
--cc=mhocko@suse.com \
--cc=qi.zheng@linux.dev \
--cc=rakie.kim@sk.com \
--cc=rppt@kernel.org \
--cc=shakeel.butt@linux.dev \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=weixugc@google.com \
--cc=ying.huang@linux.alibaba.com \
--cc=yuanchu@google.com \
--cc=ziy@nvidia.com \
/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