From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, ncardwell@google.com, yyd@google.com,
eric.dumazet@gmail.com
Subject: Re: [PATCH net-next 0/3] tcp: avoid sending too small packets
Date: Mon, 22 Apr 2024 21:30:29 +0000 [thread overview]
Message-ID: <171382142910.1995.3581375406057427614.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240418214600.1291486-1-edumazet@google.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 18 Apr 2024 21:45:57 +0000 you wrote:
> tcp_sendmsg() cooks 'large' skbs, that are later split
> if needed from tcp_write_xmit().
>
> After a split, the leftover skb size is smaller than the optimal
> size, and this causes a performance drop.
>
> In this series, tcp_grow_skb() helper is added to shift
> payload from the second skb in the write queue to the first
> skb to always send optimal sized skbs.
>
> [...]
Here is the summary with links:
- [net-next,1/3] tcp: remove dubious FIN exception from tcp_cwnd_test()
https://git.kernel.org/netdev/net-next/c/22555032c513
- [net-next,2/3] tcp: call tcp_set_skb_tso_segs() from tcp_write_xmit()
https://git.kernel.org/netdev/net-next/c/d5b38a71d333
- [net-next,3/3] tcp: try to send bigger TSO packets
https://git.kernel.org/netdev/net-next/c/8ee602c63520
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:[~2024-04-22 21:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 21:45 [PATCH net-next 0/3] tcp: avoid sending too small packets Eric Dumazet
2024-04-18 21:45 ` [PATCH net-next 1/3] tcp: remove dubious FIN exception from tcp_cwnd_test() Eric Dumazet
2024-04-18 21:45 ` [PATCH net-next 2/3] tcp: call tcp_set_skb_tso_segs() from tcp_write_xmit() Eric Dumazet
2024-04-18 21:46 ` [PATCH net-next 3/3] tcp: try to send bigger TSO packets Eric Dumazet
2025-02-13 14:45 ` Shahar Shitrit
2025-02-13 14:51 ` Eric Dumazet
2024-04-22 21: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=171382142910.1995.3581375406057427614.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=kuba@kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yyd@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).