[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <875x9xt1ha.fsf@linux.dev>
Date: Tue, 23 Dec 2025 11:57:53 -0800
From: Roman Gushchin <roman.gushchin@...ux.dev>
To: Alexei Starovoitov <alexei.starovoitov@...il.com>
Cc: Konstantin Ryabitsev <konstantin@...uxfoundation.org>, bpf
<bpf@...r.kernel.org>, linux-mm <linux-mm@...ck.org>, LKML
<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
Alexei Starovoitov <alexei.starovoitov@...il.com> writes:
> On Mon, Dec 22, 2025 at 6:42 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.
>>
>> v4:
>> - refactored memcg vm event and stat item idx checks (by Alexei)
>
> Applied yesterday.
Thank you!
> pw-bot seems to be completely broken. No notifications for the last few days.
Yep, also there were some infra issues in the ci output... Something
about git being unavailable.
Powered by blists - more mailing lists