[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<175758540901.2113906.14410248093757782465.git-patchwork-notify@kernel.org>
Date: Thu, 11 Sep 2025 10:10:09 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Jakub Kicinski <kuba@...nel.org>
Cc: davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com,
pabeni@...hat.com, andrew+netdev@...n.ch, horms@...nel.org,
daniel@...earbox.net, hawk@...nel.org, john.fastabend@...il.com,
sdf@...ichev.me, michael.chan@...adcom.com, anthony.l.nguyen@...el.com,
marcin.s.wojtas@...il.com, tariqt@...dia.com, mbloch@...dia.com,
jasowang@...hat.com, bpf@...r.kernel.org, aleksander.lobakin@...el.com,
pavan.chebbi@...adcom.com, przemyslaw.kitszel@...el.com
Subject: Re: [PATCH net-next 0/2] net: xdp: handle frags with unreadable
memory
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@...hat.com>:
On Fri, 5 Sep 2025 15:15:37 -0700 you wrote:
> Make XDP helpers compatible with unreadable memory. This is very
> similar to how we handle pfmemalloc frags today. Record the info
> in xdp_buf flags as frags get added and then update the skb once
> allocated.
>
> This series adds the unreadable memory metadata tracking to drivers
> using xdp_build_skb_from*() with no changes on the driver side - hence
> the only driver changes here are refactoring. Obviously, unreadable memory
> is incompatible with XDP today, but thanks to xdp_build_skb_from_buf()
> increasing number of drivers have a unified datapath, whether XDP is
> enabled or not.
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: xdp: pass full flags to xdp_update_skb_shared_info()
https://git.kernel.org/netdev/net-next/c/1827f773e416
- [net-next,2/2] net: xdp: handle frags with unreadable memory
https://git.kernel.org/netdev/net-next/c/6bffdc0f88f8
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