From: patchwork-bot+netdevbpf@kernel.org
To: Alexander Lobakin <aleksander.lobakin@intel.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, lorenzo@kernel.org,
dxu@dxuuu.xyz, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, john.fastabend@gmail.com, toke@kernel.org,
hawk@kernel.org, martin.lau@linux.dev, netdev@vger.kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v5 0/8] bpf: cpumap: enable GRO for XDP_PASS frames
Date: Thu, 27 Feb 2025 13:20:32 +0000 [thread overview]
Message-ID: <174066243275.1425284.11463138682186483898.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250225171751.2268401-1-aleksander.lobakin@intel.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.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
prev parent reply other threads:[~2025-02-27 13:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 17:17 Alexander Lobakin
2025-02-25 17:17 ` [PATCH net-next v5 1/8] net: gro: decouple GRO from the NAPI layer Alexander Lobakin
2025-02-25 17:17 ` [PATCH net-next v5 2/8] net: gro: expose GRO init/cleanup to use outside of NAPI Alexander Lobakin
2025-02-25 17:17 ` [PATCH net-next v5 3/8] bpf: cpumap: switch to GRO from netif_receive_skb_list() Alexander Lobakin
2025-02-25 17:17 ` [PATCH net-next v5 4/8] bpf: cpumap: reuse skb array instead of a linked list to chain skbs Alexander Lobakin
2025-02-25 17:17 ` [PATCH net-next v5 5/8] net: skbuff: introduce napi_skb_cache_get_bulk() Alexander Lobakin
2025-02-25 17:17 ` [PATCH net-next v5 6/8] bpf: cpumap: switch to napi_skb_cache_get_bulk() Alexander Lobakin
2025-02-25 17:17 ` [PATCH net-next v5 7/8] veth: use napi_skb_cache_get_bulk() instead of xdp_alloc_skb_bulk() Alexander Lobakin
2025-02-25 17:17 ` [PATCH net-next v5 8/8] xdp: remove xdp_alloc_skb_bulk() Alexander Lobakin
2025-02-27 13: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=174066243275.1425284.11463138682186483898.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dxu@dxuuu.xyz \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=toke@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
all inboxes | Powered by JetHome®