From: Eric Dumazet <edumazet@google.com>
To: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>
Cc: Simon Horman <horms@kernel.org>,
Neal Cardwell <ncardwell@google.com>,
Kuniyuki Iwashima <kuniyu@google.com>,
netdev@vger.kernel.org, eric.dumazet@gmail.com,
Eric Dumazet <edumazet@google.com>
Subject: [PATCH net-next 0/2] tcp: tcp_rcvbuf_grow() changes
Date: Mon, 17 Nov 2025 13:28:00 +0000 [thread overview]
Message-ID: <20251117132802.2083206-1-edumazet@google.com> (raw)
First pach is minor and moves tcp_moderate_rcvbuf in appropriate group.
Second patch is another attempt to keep small sk->sk_rcvbuf for DC
(small RT) TCP flows for optimal performance.
Eric Dumazet (2):
tcp: tcp_moderate_rcvbuf is only used in rx path
tcp: add net.ipv4.tcp_rtt_threshold sysctl
Documentation/networking/ip-sysctl.rst | 10 ++++++++++
.../net_cachelines/netns_ipv4_sysctl.rst | 3 ++-
include/net/netns/ipv4.h | 3 ++-
net/core/net_namespace.c | 11 ++++-------
net/ipv4/sysctl_net_ipv4.c | 9 +++++++++
net/ipv4/tcp_input.c | 18 ++++++++++++++----
net/ipv4/tcp_ipv4.c | 1 +
7 files changed, 42 insertions(+), 13 deletions(-)
--
2.52.0.rc1.455.g30608eb744-goog
next reply other threads:[~2025-11-17 13:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 13:28 Eric Dumazet [this message]
2025-11-17 13:28 ` [PATCH net-next 1/2] tcp: tcp_moderate_rcvbuf is only used in rx path Eric Dumazet
2025-11-18 4:13 ` Kuniyuki Iwashima
2025-11-17 13:28 ` [PATCH net-next 2/2] tcp: add net.ipv4.tcp_rtt_threshold sysctl Eric Dumazet
2025-11-18 4:39 ` Kuniyuki Iwashima
2025-11-18 14:04 ` Neal Cardwell
2025-11-18 16:10 ` Eric Dumazet
2025-11-18 21:14 ` Paolo Abeni
2025-11-18 21:22 ` Eric Dumazet
2025-11-19 8:01 ` Eric Dumazet
2025-11-19 8:59 ` Paolo Abeni
2025-11-19 9:07 ` Eric Dumazet
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=20251117132802.2083206-1-edumazet@google.com \
--to=edumazet@google.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.