From: patchwork-bot+netdevbpf@kernel.org
To: Pavel Begunkov <asml.silence@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
dsahern@kernel.org, edumazet@google.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/5] generic net and ipv6 minor optimisations
Date: Sat, 30 Apr 2022 12:10:12 +0000 [thread overview]
Message-ID: <165132061250.13332.11733885633402337969.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1651141755.git.asml.silence@gmail.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 28 Apr 2022 11:58:43 +0100 you wrote:
> 1-3 inline simple functions that only reshuffle arguments possibly adding
> extra zero args, and call another function. It was benchmarked before with
> a bunch of extra patches, see for details
>
> https://lore.kernel.org/netdev/cover.1648981570.git.asml.silence@gmail.com/
>
> It may increase the binary size, but it's the right thing to do and at least
> without modules it actually sheds some bytes for some standard-ish config.
>
> [...]
Here is the summary with links:
- [net-next,1/5] net: inline sock_alloc_send_skb
https://git.kernel.org/netdev/net-next/c/de32bc6aad09
- [net-next,2/5] net: inline skb_zerocopy_iter_dgram
https://git.kernel.org/netdev/net-next/c/657dd5f97b2e
- [net-next,3/5] net: inline dev_queue_xmit()
https://git.kernel.org/netdev/net-next/c/c526fd8f9f4f
- [net-next,4/5] ipv6: help __ip6_finish_output() inlining
https://git.kernel.org/netdev/net-next/c/4b143ed7dde5
- [net-next,5/5] ipv6: refactor ip6_finish_output2()
https://git.kernel.org/netdev/net-next/c/58f71be58b87
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:[~2022-04-30 12:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 10:58 [PATCH net-next 0/5] generic net and ipv6 minor optimisations Pavel Begunkov
2022-04-28 10:58 ` [PATCH net-next 1/5] net: inline sock_alloc_send_skb Pavel Begunkov
2022-04-28 10:58 ` [PATCH net-next 2/5] net: inline skb_zerocopy_iter_dgram Pavel Begunkov
2022-04-28 10:58 ` [PATCH net-next 3/5] net: inline dev_queue_xmit() Pavel Begunkov
2022-04-28 10:58 ` [PATCH net-next 4/5] ipv6: help __ip6_finish_output() inlining Pavel Begunkov
2022-04-28 10:58 ` [PATCH net-next 5/5] ipv6: refactor ip6_finish_output2() Pavel Begunkov
2022-04-30 12: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=165132061250.13332.11733885633402337969.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=asml.silence@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).