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: split tcp_check_space() in two parts
Date: Thu, 05 Feb 2026 04:50:17 +0000 [thread overview]
Message-ID: <177026701757.165764.8982996972541300841.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260203050932.3522221-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 05:09:32 +0000 you wrote:
> tcp_check_space() is fat and not inlined.
>
> Move its slow path in (out of line) __tcp_check_space()
> and make tcp_check_space() an inline function for better TCP performance.
>
> $ scripts/bloat-o-meter -t vmlinux.old vmlinux.new
> add/remove: 2/2 grow/shrink: 4/0 up/down: 708/-582 (126)
> Function old new delta
> __tcp_check_space - 521 +521
> tcp_rcv_established 1860 1916 +56
> tcp_rcv_state_process 3342 3384 +42
> tcp_event_new_data_sent 248 286 +38
> tcp_data_snd_check 71 106 +35
> __pfx___tcp_check_space - 16 +16
> __pfx_tcp_check_space 16 - -16
> tcp_check_space 566 - -566
> Total: Before=24896373, After=24896499, chg +0.00%
>
> [...]
Here is the summary with links:
- [net-next] tcp: split tcp_check_space() in two parts
https://git.kernel.org/netdev/net-next/c/309dd9942155
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 5:09 [PATCH net-next] tcp: split tcp_check_space() in two parts Eric Dumazet
2026-02-04 0:30 ` 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=177026701757.165764.8982996972541300841.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