From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, ncardwell@google.com, kuniyu@amazon.com,
kernelxing@tencent.com, horms@kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH net-next 0/5] tcp: allow to reduce max RTO
Date: Tue, 11 Feb 2025 12:30:32 +0000 [thread overview]
Message-ID: <173927703276.4031056.4714016654809718532.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250207152830.2527578-1-edumazet@google.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 7 Feb 2025 15:28:25 +0000 you wrote:
> 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.
>
> [...]
Here is the summary with links:
- [net-next,1/5] tcp: remove tcp_reset_xmit_timer() @max_when argument
https://git.kernel.org/netdev/net-next/c/0fed463777b8
- [net-next,2/5] tcp: add a @pace_delay parameter to tcp_reset_xmit_timer()
https://git.kernel.org/netdev/net-next/c/7baa030155e8
- [net-next,3/5] tcp: use tcp_reset_xmit_timer()
https://git.kernel.org/netdev/net-next/c/48b69b4c7e5d
- [net-next,4/5] tcp: add the ability to control max RTO
https://git.kernel.org/netdev/net-next/c/54a378f43425
- [net-next,5/5] tcp: add tcp_rto_max_ms sysctl
https://git.kernel.org/netdev/net-next/c/1280c26228bd
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-02-11 12:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 15:28 [PATCH net-next 0/5] tcp: allow to reduce max RTO Eric Dumazet
2025-02-07 15:28 ` [PATCH net-next 1/5] tcp: remove tcp_reset_xmit_timer() @max_when argument Eric Dumazet
2025-02-08 5:29 ` Jason Xing
2025-02-08 23:46 ` Neal Cardwell
2025-02-10 0:30 ` Kuniyuki Iwashima
2025-02-07 15:28 ` [PATCH net-next 2/5] tcp: add a @pace_delay parameter to tcp_reset_xmit_timer() Eric Dumazet
2025-02-08 5:31 ` Jason Xing
2025-02-08 23:46 ` Neal Cardwell
2025-02-10 0:32 ` Kuniyuki Iwashima
2025-02-07 15:28 ` [PATCH net-next 3/5] tcp: use tcp_reset_xmit_timer() Eric Dumazet
2025-02-08 5:32 ` Jason Xing
2025-02-08 23:47 ` Neal Cardwell
2025-02-10 0:36 ` Kuniyuki Iwashima
2025-02-07 15:28 ` [PATCH net-next 4/5] tcp: add the ability to control max RTO Eric Dumazet
2025-02-08 5:36 ` Jason Xing
2025-02-08 23:47 ` Neal Cardwell
2025-02-10 8:18 ` Eric Dumazet
2025-02-10 8:28 ` Jason Xing
2025-02-10 0:43 ` Kuniyuki Iwashima
2025-02-07 15:28 ` [PATCH net-next 5/5] tcp: add tcp_rto_max_ms sysctl Eric Dumazet
2025-02-08 5:45 ` Jason Xing
2025-02-08 23:48 ` Neal Cardwell
2025-02-10 0:46 ` Kuniyuki Iwashima
2025-02-11 12:30 ` patchwork-bot+netdevbpf [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=173927703276.4031056.4714016654809718532.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=kernelxing@tencent.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).