[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87cy439x8a.fsf@linux.dev>
Date: Wed, 24 Dec 2025 17:16:53 -0800
From: Roman Gushchin <roman.gushchin@...ux.dev>
To: Yafang Shao <laoar.shao@...il.com>
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
Yafang Shao <laoar.shao@...il.com> writes:
> 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]
Hello Yafang,
this is in my plan for next few weeks: I'll probably try to upstream
it altogether with bpfoom, but if there will be any delays with bpfoom,
we can split the patchset further.
Thanks!
Powered by blists - more mailing lists