From: Daniel Sedlak <daniel.sedlak@cdn77.com>
To: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Neal Cardwell <ncardwell@google.com>,
Kuniyuki Iwashima <kuniyu@google.com>,
David Ahern <dsahern@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Shakeel Butt <shakeel.butt@linux.dev>,
Yosry Ahmed <yosry.ahmed@linux.dev>,
linux-mm@kvack.org, netdev@vger.kernel.org
Cc: Daniel Sedlak <daniel.sedlak@cdn77.com>,
linux-trace-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: [PATCH v2 net-next 0/2] account for TCP memory pressure signaled by cgroup
Date: Mon, 14 Jul 2025 16:36:11 +0200 [thread overview]
Message-ID: <20250714143613.42184-1-daniel.sedlak@cdn77.com> (raw)
Greetings kernel wizards,
To summarize from the commit messages, the attached patches are the
result of our recent debugging sessions, where we were hunting sudden
TCP network throughput drops, where the throughput dropped from tens of
Gbps to a few Mbps for an undeterministic amount of time.
The first patch adds a new counter for netstat, so users can notice that
the sockets are marked as under pressure. The second patch adds a new
tracepoint so it is easier to pinpoint which exact cgroup is having
difficulties.
Individual commit messages should contain more detailed reasoning.
Thanks!
Daniel
Changes:
v1 -> v2:
Add tracepoint
Link: https://lore.kernel.org/netdev/20250707105205.222558-1-daniel.sedlak@cdn77.com/
Daniel Sedlak (1):
tcp: account for memory pressure signaled by cgroup
Matyas Hurtik (1):
mm/vmpressure: add tracepoint for socket pressure detection
.../networking/net_cachelines/snmp.rst | 1 +
include/net/tcp.h | 14 ++++++-----
include/trace/events/memcg.h | 25 +++++++++++++++++++
include/uapi/linux/snmp.h | 1 +
mm/vmpressure.c | 3 +++
net/ipv4/proc.c | 1 +
6 files changed, 39 insertions(+), 6 deletions(-)
cc: linux-trace-kernel@vger.kernel.org
cc: linux-doc@vger.kernel.org
cc: Steven Rostedt <rostedt@goodmis.org>
cc: Masami Hiramatsu <mhiramat@kernel.org>
cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
base-commit: e96ee511c906c59b7c4e6efd9d9b33917730e000
--
2.39.5
next reply other threads:[~2025-07-14 14:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 14:36 Daniel Sedlak [this message]
2025-07-14 14:36 ` [PATCH v2 net-next 1/2] tcp: account for " Daniel Sedlak
2025-07-16 16:49 ` Shakeel Butt
2025-07-16 18:07 ` Kuniyuki Iwashima
2025-07-16 18:37 ` Shakeel Butt
2025-07-17 15:31 ` Daniel Sedlak
2025-07-17 17:26 ` Kuniyuki Iwashima
2025-07-14 14:36 ` [PATCH v2 net-next 2/2] mm/vmpressure: add tracepoint for socket pressure detection Daniel Sedlak
2025-07-14 18:02 ` Kuniyuki Iwashima
2025-07-15 7:01 ` Daniel Sedlak
2025-07-15 17:17 ` Kuniyuki Iwashima
2025-07-15 17:46 ` Kuniyuki Iwashima
2025-07-16 8:47 ` Daniel Sedlak
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=20250714143613.42184-1-daniel.sedlak@cdn77.com \
--to=daniel.sedlak@cdn77.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rostedt@goodmis.org \
--cc=shakeel.butt@linux.dev \
--cc=yosry.ahmed@linux.dev \
/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