[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALOAHbAQQ59mSmh8aO47jnDjOu9S+FESxKw+YUp9g2Q2qvqedA@mail.gmail.com>
Date: Wed, 24 Dec 2025 11:01:18 +0800
From: Yafang Shao <laoar.shao@...il.com>
To: Roman Gushchin <roman.gushchin@...ux.dev>
Cc: bpf@...r.kernel.org, linux-mm@...ck.org, linux-kernel@...r.kernel.org,
JP Kobryn <inwardvessel@...il.com>, Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>, Shakeel Butt <shakeel.butt@...ux.dev>,
Michal Hocko <mhocko@...nel.org>, Johannes Weiner <hannes@...xchg.org>
Subject: Re: [PATCH bpf-next v4 0/6] mm: bpf kfuncs to access memcg data
On Tue, Dec 23, 2025 at 12:43 PM Roman Gushchin
<roman.gushchin@...ux.dev> wrote:
>
> Introduce kfuncs to simplify the access to the memcg data.
> These kfuncs can be used to accelerate monitoring use cases and
> for implementing custom OOM policies once BPF OOM is landed.
>
> This patchset was separated out from the BPF OOM patchset to simplify
> the logistics and accelerate the landing of the part which is useful
> by itself. No functional changes since BPF OOM v2.
Hello Roman,
Thanks for driving the BPF-MM upstreaming work—this is great progress.
Would it be possible to upstream the bpf_st_ops and cgroups patch as a
standalone series as well? [0]
While the upstreaming of BPF-THP is currently stalled, we are actively
experimenting with more BPF-MM related features—like BPF-based NUMA
balancing—on our production servers. This work is a great fit for
per-cgroup tuning via BPF, and having your bpf_st_ops and cgroups
changes upstream would be very helpful for these efforts.
[0] https://lore.kernel.org/bpf/CAADnVQJGiH_yF=AoFSRy4zh20uneJgBfqGshubLM6aVq069Fhg@mail.gmail.com/
--
Regards
Yafang
Powered by blists - more mailing lists