[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<170744702682.13594.15329078929458071578.git-patchwork-notify@kernel.org>
Date: Fri, 09 Feb 2024 02:50:26 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Magnus Karlsson <magnus.karlsson@...il.com>
Cc: magnus.karlsson@...el.com, bjorn@...nel.org, ast@...nel.org,
daniel@...earbox.net, netdev@...r.kernel.org, maciej.fijalkowski@...el.com,
kuba@...nel.org, toke@...hat.com, pabeni@...hat.com, davem@...emloft.net,
j.vosburgh@...il.com, andy@...yhouse.net, hawk@...nel.org,
john.fastabend@...il.com, edumazet@...gle.com, lorenzo@...nel.org,
bpf@...r.kernel.org, prbatra.mail@...il.com
Subject: Re: [PATCH net v2] bonding: do not report NETDEV_XDP_ACT_XSK_ZEROCOPY
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Wed, 7 Feb 2024 09:47:36 +0100 you wrote:
> From: Magnus Karlsson <magnus.karlsson@...el.com>
>
> Do not report the XDP capability NETDEV_XDP_ACT_XSK_ZEROCOPY as the
> bonding driver does not support XDP and AF_XDP in zero-copy mode even
> if the real NIC drivers do.
>
> Note that the driver used to report everything as supported before a
> device was bonded. Instead of just masking out the zero-copy support
> from this, have the driver report that no XDP feature is supported
> until a real device is bonded. This seems to be more truthful as it is
> the real drivers that decide what XDP features are supported.
>
> [...]
Here is the summary with links:
- [net,v2] bonding: do not report NETDEV_XDP_ACT_XSK_ZEROCOPY
https://git.kernel.org/netdev/net/c/9b0ed890ac2a
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