linux-kernel - Re: [PATCH net-next v5 0/8] bpf: cpumap: enable GRO for XDP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: 
 <174066243275.1425284.11463138682186483898.git-patchwork-notify@kernel.org>
Date: Thu, 27 Feb 2025 13:20:32 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Alexander Lobakin <aleksander.lobakin@...el.com>
Cc: andrew+netdev@...n.ch, davem@...emloft.net, edumazet@...gle.com,
 kuba@...nel.org, pabeni@...hat.com, lorenzo@...nel.org, dxu@...uu.xyz,
 ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
 john.fastabend@...il.com, toke@...nel.org, hawk@...nel.org,
 martin.lau@...ux.dev, netdev@...r.kernel.org, bpf@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next v5 0/8] bpf: cpumap: enable GRO for XDP_PASS frames

Hello:

This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@...hat.com>:

On Tue, 25 Feb 2025 18:17:42 +0100 you wrote:
> Several months ago, I had been looking through my old XDP hints tree[0]
> to check whether some patches not directly related to hints can be sent
> standalone. Roughly at the same time, Daniel appeared and asked[1] about
> GRO for cpumap from that tree.
> 
> Currently, cpumap uses its own kthread which processes cpumap-redirected
> frames by batches of 8, without any weighting (but with rescheduling
> points). The resulting skbs get passed to the stack via
> netif_receive_skb_list(), which means no GRO happens.
> Even though we can't currently pass checksum status from the drivers,
> in many cases GRO performs better than the listified Rx without the
> aggregation, confirmed by tests.
> 
> [...]

Here is the summary with links:
  - [net-next,v5,1/8] net: gro: decouple GRO from the NAPI layer
    (no matching commit)
  - [net-next,v5,2/8] net: gro: expose GRO init/cleanup to use outside of NAPI
    https://git.kernel.org/netdev/net-next/c/388d31417ce0
  - [net-next,v5,3/8] bpf: cpumap: switch to GRO from netif_receive_skb_list()
    https://git.kernel.org/netdev/net-next/c/4f8ab26a034f
  - [net-next,v5,4/8] bpf: cpumap: reuse skb array instead of a linked list to chain skbs
    https://git.kernel.org/netdev/net-next/c/57efe762cd3c
  - [net-next,v5,5/8] net: skbuff: introduce napi_skb_cache_get_bulk()
    https://git.kernel.org/netdev/net-next/c/859d6acd94cc
  - [net-next,v5,6/8] bpf: cpumap: switch to napi_skb_cache_get_bulk()
    (no matching commit)
  - [net-next,v5,7/8] veth: use napi_skb_cache_get_bulk() instead of xdp_alloc_skb_bulk()
    https://git.kernel.org/netdev/net-next/c/1c5bf4de975d
  - [net-next,v5,8/8] xdp: remove xdp_alloc_skb_bulk()
    https://git.kernel.org/netdev/net-next/c/b696d289c07d

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html