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 sk_forced_mem_schedule() to tcp.c
Date: Tue, 27 Jan 2026 14:10:05 +0000 [thread overview]
Message-ID: <176952300535.857293.13184901882217765162.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260123111605.4089200-1-edumazet@google.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 23 Jan 2026 11:16:05 +0000 you wrote:
> TCP fast path can (auto)inline this helper, instead
> of (auto)inling it from tcp_send_fin().
>
> No change of overall code size, but tcp_sendmsg() is faster.
>
> $ scripts/bloat-o-meter -t vmlinux.old vmlinux.new
> add/remove: 0/0 grow/shrink: 1/1 up/down: 141/-140 (1)
> Function old new delta
> tcp_stream_alloc_skb 216 357 +141
> tcp_send_fin 688 548 -140
> Total: Before=22236729, After=22236730, chg +0.00%
>
> [...]
Here is the summary with links:
- [net-next] tcp: move sk_forced_mem_schedule() to tcp.c
https://git.kernel.org/netdev/net-next/c/a18056a6c11c
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-01-27 14:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 11:16 [PATCH net-next] tcp: move sk_forced_mem_schedule() to tcp.c Eric Dumazet
2026-01-23 15:52 ` Neal Cardwell
2026-01-26 8:18 ` Paolo Abeni
2026-01-26 8:45 ` Eric Dumazet
2026-01-27 1:56 ` Jason Xing
2026-01-27 2:06 ` Eric Dumazet
2026-01-27 6:15 ` Jason Xing
2026-01-27 14:10 ` 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=176952300535.857293.13184901882217765162.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