linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Usama Arif <usamaarif642@gmail.com>
To: Casey Chen <cachen@purestorage.com>,
	akpm@linux-foundation.org, surenb@google.com
Cc: kent.overstreet@linux.dev, corbet@lwn.net, dennis@kernel.org,
	tj@kernel.org, cl@gentwo.org, vbabka@suse.cz, mhocko@suse.com,
	jackmanb@google.com, hannes@cmpxchg.org, ziy@nvidia.com,
	rientjes@google.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, souravpanda@google.com, 00107082@163.com,
	pyy@meta.com
Subject: Re: [PATCH v3] alloc_tag: add per-NUMA node stats
Date: Thu, 31 Jul 2025 12:55:29 +0100	[thread overview]
Message-ID: <2f73f1d9-ad0c-40db-9697-3070cd52f688@gmail.com> (raw)
In-Reply-To: <20250711002322.1303421-1-cachen@purestorage.com>



On 11/07/2025 01:23, Casey Chen wrote:
> This patch adds per-NUMA node breakdown of memory allocation,
> enabling more precise visibility into memory usage patterns across nodes.
> It is particularly valuable in cloud environments,
> where tracking asymmetric memory usage and identifying NUMA imbalances
> down to the allocation caller helps optimize memory efficiency, avoid
> CPU stranding, and improve system responsiveness under memory pressure.
>

Hi Casey,

I was just curious how you used the output from per NUMA allocation profiling
to fix the issues above? (So that we can do that as well :)). We get a lot of
NUMA high level meminfo from /sys/devices/system/node/nodeX/vmstat.
Are there specific allocations that are more of an issue?
Do you monitor these in userspace and use maybe something like numactl/migratepages
to migrate resources to another node?

Thanks!
Usama

      parent reply	other threads:[~2025-07-31 11:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-11  0:23 [PATCH v3] alloc_tag: add per-NUMA node stats Casey Chen
2025-07-11  0:42 ` Casey Chen
2025-07-11  0:53   ` Kent Overstreet
2025-07-11  1:07     ` Casey Chen
2025-07-11  3:09       ` Kent Overstreet
2025-07-11 17:41         ` Casey Chen
2025-07-11 18:14           ` Kent Overstreet
2025-07-11  4:14   ` David Wang
2025-07-24  0:37     ` Casey Chen
2025-07-31 11:55 ` Usama Arif [this message]

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=2f73f1d9-ad0c-40db-9697-3070cd52f688@gmail.com \
    --to=usamaarif642@gmail.com \
    --cc=00107082@163.com \
    --cc=akpm@linux-foundation.org \
    --cc=cachen@purestorage.com \
    --cc=cl@gentwo.org \
    --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=pyy@meta.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;
as well as URLs for NNTP newsgroup(s).