From: Shakeel Butt <shakeel.butt@linux.dev>
To: Daniel Sedlak <daniel.sedlak@cdn77.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Muchun Song <muchun.song@linux.dev>, Tejun Heo <tj@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Kuniyuki Iwashima <kuniyu@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Willem de Bruijn <willemb@google.com>,
Jakub Kicinski <kuba@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Matyas Hurtik <matyas.hurtik@cdn77.com>,
Simon Horman <horms@kernel.org>,
Neal Cardwell <ncardwell@google.com>,
Wei Wang <weibunny@meta.com>,
netdev@vger.kernel.org, linux-mm@kvack.org,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
Meta kernel team <kernel-team@meta.com>
Subject: Re: [PATCH] memcg: net: track network throttling due to memcg memory pressure
Date: Fri, 17 Oct 2025 14:21:02 -0700 [thread overview]
Message-ID: <cyg7k36ohtg3irtz7qqlyzsgh27ewibbsornq6xe2cjw66zsy7@cjpxycqwgigy> (raw)
In-Reply-To: <209038ea-e4fa-423c-a488-a86194cd5b04@cdn77.com>
On Fri, Oct 17, 2025 at 04:15:18PM +0200, Daniel Sedlak wrote:
> 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?
Yes please, send them out.
prev parent reply other threads:[~2025-10-17 21:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 1:31 Shakeel Butt
2025-10-16 1:40 ` Roman Gushchin
2025-10-16 5:46 ` Kuniyuki Iwashima
2025-10-16 15:19 ` Shakeel Butt
2025-10-16 10:42 ` Daniel Sedlak
2025-10-16 16:02 ` Shakeel Butt
2025-10-17 14:15 ` Daniel Sedlak
2025-10-17 21:21 ` Shakeel Butt [this message]
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=cyg7k36ohtg3irtz7qqlyzsgh27ewibbsornq6xe2cjw66zsy7@cjpxycqwgigy \
--to=shakeel.butt@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=daniel.sedlak@cdn77.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hannes@cmpxchg.org \
--cc=horms@kernel.org \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matyas.hurtik@cdn77.com \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=roman.gushchin@linux.dev \
--cc=tj@kernel.org \
--cc=weibunny@meta.com \
--cc=willemb@google.com \
/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