[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <54d1ac44-8e53-4056-8061-0c620d9ec4bf@redhat.com>
Date: Thu, 30 Oct 2025 11:15:18 +0100
From: Paolo Abeni <pabeni@...hat.com>
To: Jason Xing <kerneljasonxing@...il.com>, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, bjorn@...nel.org,
magnus.karlsson@...el.com, maciej.fijalkowski@...el.com,
jonathan.lemon@...il.com, sdf@...ichev.me, ast@...nel.org,
daniel@...earbox.net, hawk@...nel.org, john.fastabend@...il.com,
joe@...a.to, willemdebruijn.kernel@...il.com
Cc: bpf@...r.kernel.org, netdev@...r.kernel.org,
Jason Xing <kernelxing@...cent.com>,
Alexander Lobakin <aleksander.lobakin@...el.com>
Subject: Re: [PATCH net-next v2] xsk: add indirect call for xsk_destruct_skb
On 10/26/25 3:58 PM, Jason Xing wrote:
> From: Jason Xing <kernelxing@...cent.com>
>
> Since Eric proposed an idea about adding indirect call for UDP and
Minor nit: ^^^^^^
either 'remove an indirect call' or 'adding indirect call wrappers'
> managed to see a huge improvement[1], the same situation can also be
> applied in xsk scenario.
>
> This patch adds an indirect call for xsk and helps current copy mode
> improve the performance by around 1% stably which was observed with
> IXGBE at 10Gb/sec loaded.
If I follow the conversation correctly, Jakub's concern is mostly about
this change affecting only the copy mode.
Out of sheer ignorance on my side is not clear how frequent that
scenario is. AFAICS, applications could always do zero-copy with proper
setup, am I correct?!?
In such case I think this patch is not worth.
Otherwise, please describe/explain the real-use case needing the copy mode.
Thanks,
Paolo
Powered by blists - more mailing lists