linux-kernel - Re: [PATCH] memcg: net: track network throttling due to memcg memory pressure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <209038ea-e4fa-423c-a488-a86194cd5b04@cdn77.com>
Date: Fri, 17 Oct 2025 16:15:18 +0200
From: Daniel Sedlak <daniel.sedlak@...77.com>
To: Shakeel Butt <shakeel.butt@...ux.dev>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
 Johannes Weiner <hannes@...xchg.org>, Michal Hocko <mhocko@...nel.org>,
 Roman Gushchin <roman.gushchin@...ux.dev>,
 Muchun Song <muchun.song@...ux.dev>, Tejun Heo <tj@...nel.org>,
 Eric Dumazet <edumazet@...gle.com>, Kuniyuki Iwashima <kuniyu@...gle.com>,
 Paolo Abeni <pabeni@...hat.com>, Willem de Bruijn <willemb@...gle.com>,
 Jakub Kicinski <kuba@...nel.org>, "David S . Miller" <davem@...emloft.net>,
 Matyas Hurtik <matyas.hurtik@...77.com>, Simon Horman <horms@...nel.org>,
 Neal Cardwell <ncardwell@...gle.com>, Wei Wang <weibunny@...a.com>,
 netdev@...r.kernel.org, linux-mm@...ck.org, cgroups@...r.kernel.org,
 linux-kernel@...r.kernel.org, Meta kernel team <kernel-team@...a.com>
Subject: Re: [PATCH] memcg: net: track network throttling due to memcg memory
 pressure

On 10/16/25 6:02 PM, Shakeel Butt wrote:
> On Thu, Oct 16, 2025 at 12:42:19PM +0200, Daniel Sedlak wrote:
>> On 10/16/25 3:31 AM, Shakeel Butt wrote:
>> I am curious how the future work will unfold. If you need help with future
>> developments I can help you, we have hundreds of servers where this
>> throttling is happening.
> 
> I think first thing I would like to know if this patch is a good start
> for your use-case of observability and debugging.What else do you need
> for sufficient support for your use-case?

Yes, it is a good start, we can now hook this easily into our monitoring 
system and detect affected servers more easily.

> I imagine that would be
> tracepoints to extract more information on the source of the throttling.
> If you don't mind, can you take a stab at that?

We have some tracepoints that we have used for debugging this. We would 
like to upstream them, if that makes sense to you?

Thanks!
Daniel