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, kuniyu@google.com, netdev@vger.kernel.org,
	eric.dumazet@gmail.com
Subject: Re: [PATCH net-next] net: remove addr_len argument of recvmsg() handlers
Date: Tue, 03 Mar 2026 04:47:03 +0000	[thread overview]
Message-ID: <177251322304.625663.12519588393329554160.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260227151120.1346573-1-edumazet@google.com>

Hello:

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

On Fri, 27 Feb 2026 15:11:20 +0000 you wrote:
> Use msg->msg_namelen as a place holder instead of a
> temporary variable, notably in inet[6]_recvmsg().
> 
> This removes stack canaries and allows tail-calls.
> 
> $ scripts/bloat-o-meter -t vmlinux.old vmlinux
> add/remove: 0/0 grow/shrink: 2/19 up/down: 26/-532 (-506)
> Function                                     old     new   delta
> rawv6_recvmsg                                744     767     +23
> vsock_dgram_recvmsg                           55      58      +3
> vsock_connectible_recvmsg                     50      47      -3
> unix_stream_recvmsg                          161     158      -3
> unix_seqpacket_recvmsg                        62      59      -3
> unix_dgram_recvmsg                            42      39      -3
> tcp_recvmsg                                  546     543      -3
> mptcp_recvmsg                               1568    1565      -3
> ping_recvmsg                                 806     800      -6
> tcp_bpf_recvmsg_parser                       983     974      -9
> ip_recv_error                                588     576     -12
> ipv6_recv_rxpmtu                             442     428     -14
> udp_recvmsg                                 1243    1224     -19
> ipv6_recv_error                             1046    1024     -22
> udpv6_recvmsg                               1487    1461     -26
> raw_recvmsg                                  465     437     -28
> udp_bpf_recvmsg                             1027     984     -43
> sock_common_recvmsg                          103      27     -76
> inet_recvmsg                                 257     175     -82
> inet6_recvmsg                                257     175     -82
> tcp_bpf_recvmsg                              663     568     -95
> Total: Before=25143834, After=25143328, chg -0.00%
> 
> [...]

Here is the summary with links:
  - [net-next] net: remove addr_len argument of recvmsg() handlers
    https://git.kernel.org/netdev/net-next/c/8341c989ac77

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



      parent reply	other threads:[~2026-03-03  4:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-27 15:11 [PATCH net-next] net: remove addr_len argument of recvmsg() handlers Eric Dumazet
2026-02-28 19:45 ` Willem de Bruijn
2026-03-03  4:47 ` 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=177251322304.625663.12519588393329554160.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=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 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.