[PATCH v2] net/mlx5: allow MTU mismatch for running shared Rx queues

[Raslan Darawsheh]

Hi,


On 29/01/2026 10:13 AM, Shani Peretz wrote:
> Previously, mlx5_shared_rxq_match() rejected any MTU mismatch between
> a port and the shared RX queue, even when the queue hardware was already
> running. This caused failures when hot-adding representors after runtime
> MTU changes (new port has default MTU=1500, but running queue was created
> with MTU=9000). It also prevented proper port reconfiguration scenarios.
> 
> The fix allows MTU mismatches when rxq_ctrl->obj != NULL (queue is
> running), since runtime MTU changes via rte_eth_dev_set_mtu() only update
> software bookkeeping without recreating hardware resources. Stopped queues
> still enforce MTU matching to trigger proper reconfiguration.
> 
> This patch also removes the redundant priv->mtu field and uses
> dev->data->mtu consistently for MTU tracking throughout the driver.
> 
> Fixes: 4414eb800708 ("net/mlx5: store MTU at Rx queue allocation time")
> Fixes: 09c2555303be ("net/mlx5: support shared Rx queue")
> Cc: a.schollmeyer at syseleven.de
> Cc: stable at dpdk.org
> 
> Signed-off-by: Shani Peretz <shperetz at nvidia.com>
> Acked-by: Dariusz Sosnowski <dsosnowski at nvidia.com>

Patch applied to next-net-mlx,

Kindest regards
Raslan Darawsheh