From: Kaiyang Zhao <kaiyang2@cs.cmu.edu>
To: David Rientjes <rientjes@google.com>
Cc: linux-mm@kvack.org, cgroups@vger.kernel.org,
roman.gushchin@linux.dev, shakeel.butt@linux.dev,
muchun.song@linux.dev, akpm@linux-foundation.org,
mhocko@kernel.org, nehagholkar@meta.com, abhishekd@meta.com,
hannes@cmpxchg.org
Subject: Re: [PATCH] mm,memcg: provide per-cgroup counters for NUMA balancing operations
Date: Mon, 12 Aug 2024 22:49:02 +0000 [thread overview]
Message-ID: <ZrqRXtVAkbC-q9SP@localhost.localhost> (raw)
In-Reply-To: <e34a841c-c4c6-30fd-ca20-312c84654c34@google.com>
On Sun, Aug 11, 2024 at 01:16:53PM -0700, David Rientjes wrote:
> Hi Kaiyang, have you considered per-memcg control over NUMA balancing
> operations as well?
>
> Wondering if that's the direction that you're heading in, because it would
> be very useful to be able to control NUMA balancing at memcg granularity
> on multi-tenant systems.
>
> I mentioned this at LSF/MM/BPF this year. If people believe this is out
> of scope for memcg, that would be good feedback as well.
Yes that's exactly where we are heading -- per-cgroup control of NUMA
balancing operations in the context of memory tiering with CXL memory,
by extending the concept of memory.low and memory.high. The use case is
enabling a fair share of top tier memory across containers.
I'm collaborating with Meta on this, and we already have an implementation
and some experiments done. The patches will go out soon. If others have
thoughts on this, please chime in.
Best,
Kaiyang Zhao
next prev parent reply other threads:[~2024-08-12 22:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 21:21 kaiyang2
2024-08-10 0:28 ` Andrew Morton
2024-08-11 20:16 ` David Rientjes
2024-08-12 22:49 ` Kaiyang Zhao [this message]
2024-08-13 5:09 ` David Rientjes
2024-08-13 18:21 ` Kaiyang Zhao
2024-08-14 20:48 ` Andrew Morton
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=ZrqRXtVAkbC-q9SP@localhost.localhost \
--to=kaiyang2@cs.cmu.edu \
--cc=abhishekd@meta.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=nehagholkar@meta.com \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
/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