From: patchwork-bot+netdevbpf@kernel.org
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
alexandr.lobakin@intel.com
Subject: Re: [PATCH net-next 0/9][pull request] 10GbE Intel Wired LAN Driver Updates 2021-12-28
Date: Wed, 29 Dec 2021 00:20:11 +0000 [thread overview]
Message-ID: <164073721184.15020.4929460832997879535.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211228175815.281449-1-anthony.l.nguyen@intel.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Tony Nguyen <anthony.l.nguyen@intel.com>:
On Tue, 28 Dec 2021 09:58:06 -0800 you wrote:
> Alexander Lobakin says:
>
> napi_build_skb() I introduced earlier this year ([0]) aims
> to decrease MM pressure and the overhead from in-place
> kmem_cache_alloc() on each Rx entry processing by decaching
> skbuff_heads from NAPI per-cpu cache filled prior to that by
> napi_consume_skb() (so it is sort of a direct shortcut for
> free -> mm -> alloc cycle).
> Currently, no in-tree drivers use it. Switch all Intel Ethernet
> drivers to it to get slight-to-medium perf boosts depending on
> the frame size.
>
> [...]
Here is the summary with links:
- [net-next,1/9] e1000: switch to napi_consume_skb()
https://git.kernel.org/netdev/net-next/c/dcb95f06eab8
- [net-next,2/9] e1000: switch to napi_build_skb()
https://git.kernel.org/netdev/net-next/c/89a354c03b2d
- [net-next,3/9] i40e: switch to napi_build_skb()
https://git.kernel.org/netdev/net-next/c/6e19cf7d3815
- [net-next,4/9] iavf: switch to napi_build_skb()
https://git.kernel.org/netdev/net-next/c/ef687d61e0e9
- [net-next,5/9] ice: switch to napi_build_skb()
https://git.kernel.org/netdev/net-next/c/5ce666315848
- [net-next,6/9] igb: switch to napi_build_skb()
https://git.kernel.org/netdev/net-next/c/fa441f0fa8bc
- [net-next,7/9] igc: switch to napi_build_skb()
https://git.kernel.org/netdev/net-next/c/4dd330a7e894
- [net-next,8/9] ixgbe: switch to napi_build_skb()
https://git.kernel.org/netdev/net-next/c/a39363367a37
- [net-next,9/9] ixgbevf: switch to napi_build_skb()
https://git.kernel.org/netdev/net-next/c/c15500198916
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:[~2021-12-29 0:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-28 17:58 [PATCH net-next 0/9][pull request] 10GbE Intel Wired LAN Driver Updates 2021-12-28 Tony Nguyen
2021-12-28 17:58 ` [PATCH net-next 1/9] e1000: switch to napi_consume_skb() Tony Nguyen
2021-12-28 17:58 ` [PATCH net-next 2/9] e1000: switch to napi_build_skb() Tony Nguyen
2021-12-28 17:58 ` [PATCH net-next 3/9] i40e: " Tony Nguyen
2021-12-28 17:58 ` [PATCH net-next 4/9] iavf: " Tony Nguyen
2021-12-28 17:58 ` [PATCH net-next 5/9] ice: " Tony Nguyen
2021-12-28 17:58 ` [PATCH net-next 6/9] igb: " Tony Nguyen
2021-12-28 17:58 ` [PATCH net-next 7/9] igc: " Tony Nguyen
2021-12-28 17:58 ` [PATCH net-next 8/9] ixgbe: " Tony Nguyen
2021-12-28 17:58 ` [PATCH net-next 9/9] ixgbevf: " Tony Nguyen
2021-12-29 0:20 ` 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=164073721184.15020.4929460832997879535.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandr.lobakin@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=kuba@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 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.