All of lore.kernel.org
 help / color / mirror / Atom feed
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: use skb->len instead of skb->truesize in tcp_can_ingest()
Date: Tue, 30 Sep 2025 01:30:17 +0000	[thread overview]
Message-ID: <175919581725.1779167.8436912665882904953.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250927092827.2707901-1-edumazet@google.com>

Hello:

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

On Sat, 27 Sep 2025 09:28:27 +0000 you wrote:
> Some applications are stuck to the 20th century and still use
> small SO_RCVBUF values.
> 
> After the blamed commit, we can drop packets especially
> when using LRO/hw-gro enabled NIC and small MSS (1500) values.
> 
> LRO/hw-gro NIC pack multiple segments into pages, allowing
> tp->scaling_ratio to be set to a high value.
> 
> [...]

Here is the summary with links:
  - [net-next] tcp: use skb->len instead of skb->truesize in tcp_can_ingest()
    https://git.kernel.org/netdev/net-next/c/f017c1f768b6

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



      reply	other threads:[~2025-09-30  1:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-27  9:28 [PATCH net-next] tcp: use skb->len instead of skb->truesize in tcp_can_ingest() Eric Dumazet
2025-09-30  1: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=175919581725.1779167.8436912665882904953.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 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.