On 11/22/2024 4:56 PM, Fijalkowski, Maciej wrote:
Remove the check that prevents XDP support when SRIOV is enabled.
There is no reason to completely forbid the user from using XDP
with SRIOV.
I think we need some more context here in commit message.
ixgbe HW was really short on HW queues that's why probably this restriction
was introduced in the first place.
Now I believe that driver has an ability to share XDP Tx resources with locking
being involved and that's why you can relax the previous limitation.
Correct?
Right, ixgbe hardware has a limited number of hw queues. There is
locking in place now. The reasoning behind this change is to give users
the flexibility to use XDP with SRIOV, there may be use cases for such
constrained scenarios, where this tradeoff is acceptable...
I'll update commit msg.
Reviewed-by: Przemek Kitszel <[email protected]>
Signed-off-by: Martyna Szapar-Mudlaw <martyna.szapar-
[email protected]>
---
Added CC netdev
---
drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c
b/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c
index 459a539cf8db..a07e28107a42 100644
--- a/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c
+++ b/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c
@@ -10637,9 +10637,6 @@ static int ixgbe_xdp_setup(struct net_device
*dev, struct bpf_prog *prog)
bool need_reset;
int num_queues;
- if (adapter->flags & IXGBE_FLAG_SRIOV_ENABLED)
- return -EINVAL;
-
if (adapter->flags & IXGBE_FLAG_DCB_ENABLED)
return -EINVAL;
--
2.36.1
