[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250207152830.2527578-1-edumazet@google.com>
Date: Fri, 7 Feb 2025 15:28:25 +0000
From: Eric Dumazet <edumazet@...gle.com>
To: "David S . Miller" <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>
Cc: netdev@...r.kernel.org, Neal Cardwell <ncardwell@...gle.com>,
Kuniyuki Iwashima <kuniyu@...zon.com>, Jason Xing <kernelxing@...cent.com>,
Simon Horman <horms@...nel.org>, eric.dumazet@...il.com,
Eric Dumazet <edumazet@...gle.com>
Subject: [PATCH net-next 0/5] tcp: allow to reduce max RTO
This is a followup of a discussion started 6 months ago
by Jason Xing.
Some applications want to lower the time between each
retransmit attempts.
TCP_KEEPINTVL and TCP_KEEPCNT socket options don't
work around the issue.
This series adds:
- a new TCP level socket option (TCP_RTO_MAX_MS)
- a new sysctl (/proc/sys/net/ipv4/tcp_rto_max_ms)
Admins and/or applications can now change the max rto value
at their own risk.
Link: https://lore.kernel.org/netdev/20240715033118.32322-1-kerneljasonxing@gmail.com/T/
Eric Dumazet (5):
tcp: remove tcp_reset_xmit_timer() @max_when argument
tcp: add a @pace_delay parameter to tcp_reset_xmit_timer()
tcp: use tcp_reset_xmit_timer()
tcp: add the ability to control max RTO
tcp: add tcp_rto_max_ms sysctl
Documentation/networking/ip-sysctl.rst | 13 ++++++++
.../net_cachelines/inet_connection_sock.rst | 1 +
.../net_cachelines/netns_ipv4_sysctl.rst | 1 +
include/net/inet_connection_sock.h | 1 +
include/net/netns/ipv4.h | 1 +
include/net/tcp.h | 23 +++++++++-----
include/uapi/linux/tcp.h | 1 +
net/ipv4/sysctl_net_ipv4.c | 10 ++++++
net/ipv4/tcp.c | 14 ++++++++-
net/ipv4/tcp_fastopen.c | 4 +--
net/ipv4/tcp_input.c | 19 +++++-------
net/ipv4/tcp_ipv4.c | 6 ++--
net/ipv4/tcp_output.c | 17 +++++-----
net/ipv4/tcp_timer.c | 31 ++++++++++---------
14 files changed, 93 insertions(+), 49 deletions(-)
--
2.48.1.502.g6dc24dfdaf-goog
Powered by blists - more mailing lists