From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
ncardwell@google.com, kuniyu@google.com
Subject: Re: [PATCH net] tcp: give up on stronger sk_rcvbuf checks (for now)
Date: Sat, 28 Feb 2026 16:10:10 +0000 [thread overview]
Message-ID: <177229501054.3006106.4630039623073191994.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260227003359.2391017-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 26 Feb 2026 16:33:59 -0800 you wrote:
> We hit another corner case which leads to TcpExtTCPRcvQDrop
>
> Connections which send RPCs in the 20-80kB range over loopback
> experience spurious drops. The exact conditions for most of
> the drops I investigated are that:
> - socket exchanged >1MB of data so its not completely fresh
> - rcvbuf is around 128kB (default, hasn't grown)
> - there is ~60kB of data in rcvq
> - skb > 64kB arrives
>
> [...]
Here is the summary with links:
- [net] tcp: give up on stronger sk_rcvbuf checks (for now)
https://git.kernel.org/netdev/net/c/026dfef287c0
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:[~2026-02-28 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 0:33 [PATCH net] tcp: give up on stronger sk_rcvbuf checks (for now) Jakub Kicinski
2026-02-28 3:48 ` Kuniyuki Iwashima
2026-02-28 3:51 ` Eric Dumazet
2026-02-28 16:10 ` 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=177229501054.3006106.4630039623073191994.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox