From: "Christoph Lameter (Ampere)" <cl@gentwo.org>
To: David Rientjes <rientjes@google.com>
Cc: Kent Overstreet <kent.overstreet@linux.dev>,
Casey Chen <cachen@purestorage.com>,
Andrew Morton <akpm@linux-foundation.org>,
surenb@google.com, corbet@lwn.net, dennis@kernel.org,
tj@kernel.org, Vlastimil Babka <vbabka@suse.cz>,
mhocko@suse.com, jackmanb@google.com, hannes@cmpxchg.org,
ziy@nvidia.com, roman.gushchin@linux.dev, harry.yoo@oracle.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, yzhong@purestorage.com,
Sourav Panda <souravpanda@google.com>
Subject: Re: [PATCH] alloc_tag: add per-NUMA node stats
Date: Tue, 8 Jul 2025 15:38:24 -0700 (PDT) [thread overview]
Message-ID: <7a9fc525-7ed5-367c-6504-5ce9ab4520b7@gentwo.org> (raw)
In-Reply-To: <3c9b5773-83ed-4f13-11a8-fcc162c8c483@google.com>
On Tue, 8 Jul 2025, David Rientjes wrote:
> Right, per-node memory attribution, or per zone, is very useful.
I thought that was already possible using cgroups? That way you have the
numbers for an application which may be much more useful.
next prev parent reply other threads:[~2025-07-08 22:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 23:30 Casey Chen
2025-06-11 1:21 ` Andrew Morton
2025-06-11 1:33 ` Casey Chen
2025-06-11 3:47 ` Kent Overstreet
2025-06-11 3:41 ` Kent Overstreet
2025-06-12 5:36 ` David Wang
2025-06-12 15:37 ` Kent Overstreet
2025-06-18 22:16 ` Kent Overstreet
2025-07-08 21:52 ` David Rientjes
2025-07-08 22:38 ` Christoph Lameter (Ampere) [this message]
2025-07-09 19:14 ` David Rientjes
2025-07-08 22:53 ` Casey Chen
2025-07-08 23:07 ` Casey Chen
2025-07-10 5:54 ` Sourav Panda
-- strict thread matches above, loose matches on Subject: below --
2025-05-30 0:39 [PATCH 0/1] alloc_tag: add per-numa " Casey Chen
2025-05-30 0:39 ` [PATCH] " Casey 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=7a9fc525-7ed5-367c-6504-5ce9ab4520b7@gentwo.org \
--to=cl@gentwo.org \
--cc=akpm@linux-foundation.org \
--cc=cachen@purestorage.com \
--cc=corbet@lwn.net \
--cc=dennis@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=harry.yoo@oracle.com \
--cc=jackmanb@google.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=souravpanda@google.com \
--cc=surenb@google.com \
--cc=tj@kernel.org \
--cc=vbabka@suse.cz \
--cc=yzhong@purestorage.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