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, kuniyu@google.com,
netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH net-next] tcp: move tcp_rbtree_insert() to tcp_output.c
Date: Thu, 05 Feb 2026 04:50:12 +0000 [thread overview]
Message-ID: <177026701208.165764.18371893962289031802.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260203045110.3499713-1-edumazet@google.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 3 Feb 2026 04:51:10 +0000 you wrote:
> tcp_rbtree_insert() is primarily used from tcp_output.c
> In tcp_input.c, only (slow path) tcp_collapse() uses it.
>
> Move it to tcp_output.c to allow its (auto)inlining to improve
> TCP tx fast path.
>
> $ scripts/bloat-o-meter -t vmlinux.old vmlinux.new
> add/remove: 0/0 grow/shrink: 4/1 up/down: 445/-115 (330)
> Function old new delta
> tcp_connect 4277 4478 +201
> tcp_event_new_data_sent 162 248 +86
> tcp_send_synack 780 862 +82
> tcp_fragment 1185 1261 +76
> tcp_collapse 1524 1409 -115
> Total: Before=24896043, After=24896373, chg +0.00%
>
> [...]
Here is the summary with links:
- [net-next] tcp: move tcp_rbtree_insert() to tcp_output.c
https://git.kernel.org/netdev/net-next/c/7c1db78ff75f
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-05 4:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 4:51 [PATCH net-next] tcp: move tcp_rbtree_insert() to tcp_output.c Eric Dumazet
2026-02-04 0:27 ` Kuniyuki Iwashima
2026-02-05 4:50 ` 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=177026701208.165764.18371893962289031802.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 \
/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