All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	kuniyu@google.com, ncardwell@google.com, horms@kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/5] tcp: better visibility when receive queues are full
Date: Tue, 17 Nov 2026 03:20:08 +0000	[thread overview]
Message-ID: <179488560802.316053.11655745821190774508.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261114155150.235743-1-edumazet@kernel.org>

Hello:

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

On Sat, 14 Nov 2026 16:51:45 +0100 you wrote:
> When a TCP socket can not queue an incoming packet, it is currently
> hard to tell why, and how often the stack had to work to make room.
> 
> Patch 1 adds TcpExtTCPRcvCollapseSkipped, counting the collapses
> skipped by the rate limit added in commit c2213d9b61c1 ("tcp: rate
> limit receive queue collapsing"). Patch 2 is the packetdrill test
> for this rate limit.
> 
> [...]

Here is the summary with links:
  - [net-next,1/5] tcp: add TCPRcvCollapseSkipped counter
    https://git.kernel.org/netdev/net-next/c/7bf8b8ce32a5
  - [net-next,2/5] selftests/net: packetdrill: add tcp_rcv_collapse_ratelimit.pkt
    https://git.kernel.org/netdev/net-next/c/32d99662c363
  - [net-next,3/5] tcp: use SKB_DROP_REASON_SOCKET_RCVBUFF when over sk_rcvbuf
    https://git.kernel.org/netdev/net-next/c/27a46d593d89
  - [net-next,4/5] net: add SKB_DROP_REASON_MEMCG
    https://git.kernel.org/netdev/net-next/c/a2f25e291be5
  - [net-next,5/5] selftests/net: packetdrill: add tcp_rcv_collapse.pkt
    https://git.kernel.org/netdev/net-next/c/756561fcd216

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-17  3:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-14 15:51 [PATCH net-next 0/5] tcp: better visibility when receive queues are full Eric Dumazet
2026-11-14 15:51 ` [PATCH net-next 1/5] tcp: add TCPRcvCollapseSkipped counter Eric Dumazet
2026-11-14 16:28   ` Kuniyuki Iwashima
2026-11-14 15:51 ` [PATCH net-next 2/5] selftests/net: packetdrill: add tcp_rcv_collapse_ratelimit.pkt Eric Dumazet
2026-11-14 16:34   ` Kuniyuki Iwashima
2026-11-14 15:51 ` [PATCH net-next 3/5] tcp: use SKB_DROP_REASON_SOCKET_RCVBUFF when over sk_rcvbuf Eric Dumazet
2026-11-14 16:36   ` Kuniyuki Iwashima
2026-11-14 15:51 ` [PATCH net-next 4/5] net: add SKB_DROP_REASON_MEMCG Eric Dumazet
2026-11-14 16:43   ` Kuniyuki Iwashima
2026-11-14 15:51 ` [PATCH net-next 5/5] selftests/net: packetdrill: add tcp_rcv_collapse.pkt Eric Dumazet
2026-11-14 16:49   ` Kuniyuki Iwashima
2026-11-17  3:17 ` [PATCH net-next 0/5] tcp: better visibility when receive queues are full Jakub Kicinski
2026-11-17  9:21   ` Eric Dumazet
2026-11-17  3:20 ` 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=179488560802.316053.11655745821190774508.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.