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, namangulati@google.com,
eric.dumazet@gmail.com
Subject: Re: [PATCH net-next] tcp: remove some holes in struct tcp_sock
Date: Thu, 29 Feb 2024 04:40:27 +0000 [thread overview]
Message-ID: <170918162707.21906.9269286633146762240.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240227192721.3558982-1-edumazet@google.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 27 Feb 2024 19:27:21 +0000 you wrote:
> By moving some fields around, this patch shrinks
> holes size from 56 to 32, saving 24 bytes on 64bit arches.
>
> After the patch pahole gives the following for 'struct tcp_sock':
>
> /* size: 2304, cachelines: 36, members: 162 */
> /* sum members: 2234, holes: 6, sum holes: 32 */
> /* sum bitfield members: 34 bits, bit holes: 5, sum bit holes: 14 bits */
> /* padding: 32 */
> /* paddings: 3, sum paddings: 10 */
> /* forced alignments: 1, forced holes: 1, sum forced holes: 12 */
>
> [...]
Here is the summary with links:
- [net-next] tcp: remove some holes in struct tcp_sock
https://git.kernel.org/netdev/net-next/c/99123622050f
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-02-29 4:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 19:27 [PATCH net-next] tcp: remove some holes in struct tcp_sock Eric Dumazet
2024-02-28 7:56 ` Jiri Pirko
2024-02-29 4:40 ` 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=170918162707.21906.9269286633146762240.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=namangulati@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