Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@kernel.org>
Cc: kuba@kernel.org, pabeni@redhat.com, davem@davemloft.net,
	netdev@vger.kernel.org, horms@kernel.org, ncardwell@google.com,
	kuniyu@google.com, willemb@google.com, mason@kernel.org
Subject: Re: [PATCH net] tcp: rate limit receive queue collapsing
Date: Mon, 09 Nov 2026 23:00:12 +0000	[thread overview]
Message-ID: <179426521242.3532311.12175474305421546096.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261105124043.1543405-1-edumazet@kernel.org>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu,  5 Nov 2026 13:40:43 +0100 you wrote:
> When a socket is over its receive buffer limit and its sk_rcvbuf can
> not grow, every incoming segment that needs memory goes through
> tcp_prune_queue(), which runs tcp_collapse_ofo_queue() and tcp_collapse()
> on the receive queue. Both walk their whole queue, even when there is
> nothing left to collapse.
> 
> A peer can trigger this walk per packet, without refilling memory:
> 
> [...]

Here is the summary with links:
  - [net] tcp: rate limit receive queue collapsing
    https://git.kernel.org/netdev/net/c/c2213d9b61c1

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-11-09 23:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05 12:40 [PATCH net] tcp: rate limit receive queue collapsing Eric Dumazet
2026-11-05 12:44 ` netdev-bot+sinfo
2026-11-05 15:07 ` Willem de Bruijn
2026-11-05 20:12 ` Kuniyuki Iwashima
2026-11-05 21:57   ` Neal Cardwell
2026-11-09 23: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=179426521242.3532311.12175474305421546096.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=mason@kernel.org \
    --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