From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, ncardwell@google.com, willemb@google.com,
kuniyu@google.com, netdev@vger.kernel.org,
eric.dumazet@gmail.com
Subject: Re: [PATCH net-next] tcp: better handle TCP_TX_DELAY on established flows
Date: Wed, 15 Oct 2025 16:00:08 +0000 [thread overview]
Message-ID: <176054400824.936044.998951692022220635.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251013145926.833198-1-edumazet@google.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 13 Oct 2025 14:59:26 +0000 you wrote:
> Some applications uses TCP_TX_DELAY socket option after TCP flow
> is established.
>
> Some metrics need to be updated, otherwise TCP might take time to
> adapt to the new (emulated) RTT.
>
> This patch adjusts tp->srtt_us, tp->rtt_min, icsk_rto
> and sk->sk_pacing_rate.
>
> [...]
Here is the summary with links:
- [net-next] tcp: better handle TCP_TX_DELAY on established flows
https://git.kernel.org/netdev/net-next/c/1c51450f1aff
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-10-15 16:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 14:59 [PATCH net-next] tcp: better handle TCP_TX_DELAY on established flows Eric Dumazet
2025-10-14 8:22 ` Paolo Abeni
2025-10-14 8:29 ` Eric Dumazet
2025-10-14 8:54 ` Eric Dumazet
2025-10-14 9:37 ` Paolo Abeni
2025-10-14 9:40 ` Eric Dumazet
2025-10-14 16:06 ` Jakub Kicinski
2025-10-14 16:16 ` Eric Dumazet
2025-10-14 17:04 ` Jakub Kicinski
2025-10-14 9:38 ` Eric Dumazet
2025-10-15 2:34 ` Jakub Kicinski
2025-10-15 5:17 ` Eric Dumazet
2025-10-15 16:00 ` 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=176054400824.936044.998951692022220635.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=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).