[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <168238861870.3463.8505415279039848704.git-patchwork-notify@kernel.org>
Date: Tue, 25 Apr 2023 02:10:18 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Horatiu Vultur <horatiu.vultur@...rochip.com>
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
bpf@...r.kernel.org, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, ast@...nel.org,
daniel@...earbox.net, hawk@...nel.org, john.fastabend@...il.com,
aleksander.lobakin@...el.com, maciej.fijalkowski@...el.com,
UNGLinuxDriver@...rochip.com
Subject: Re: [PATCH net-next v3] lan966x: Don't use xdp_frame when action is
XDP_TX
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Sat, 22 Apr 2023 16:23:44 +0200 you wrote:
> When the action of an xdp program was XDP_TX, lan966x was creating
> a xdp_frame and use this one to send the frame back. But it is also
> possible to send back the frame without needing a xdp_frame, because
> it is possible to send it back using the page.
> And then once the frame is transmitted is possible to use directly
> page_pool_recycle_direct as lan966x is using page pools.
> This would save some CPU usage on this path, which results in higher
> number of transmitted frames. Bellow are the statistics:
> Frame size: Improvement:
> 64 ~8%
> 256 ~11%
> 512 ~8%
> 1000 ~0%
> 1500 ~0%
>
> [...]
Here is the summary with links:
- [net-next,v3] lan966x: Don't use xdp_frame when action is XDP_TX
https://git.kernel.org/netdev/net-next/c/700f11eb2cbe
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists