net/mlx5: fix RETA update without stopping device
The global redirection table is used to create the default flow
rules for the ingress traffic with the lowest priority. It is also
used to create the default RSS rule in the destination table when
there is a tunnel offload.
To update the RETA in-flight, there is no restriction in the ethdev
API. In the previous implementation of mlx5, a port restart was
needed to make the new configuration take effect.
The restart is heavy, e.g., all the queues will be released and
reallocated, users' rules will be flushed. Since the restart is
internal, there is a risk to crash the application when some change
in the ethdev is introduced but no workaround is done in mlx5 PMD.
The users' rules, including the default miss rule for tunnel
offload, should not be impacted by the RETA update. It is improper
to flush all rules when updating RETA.
With this patch, only the default rules will be flushed and
re-created with the new table configuration.
Fixes: 3f2fe392bd
("net/mlx5: fix crash during RETA update")
Cc: stable@dpdk.org
Signed-off-by: Bing Zhao <bingz@nvidia.com>
Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
This commit is contained in:
parent
a9b6ea45be
commit
6b5b3005cb
@ -218,12 +218,6 @@ mlx5_dev_rss_reta_update(struct rte_eth_dev *dev,
|
|||||||
MLX5_ASSERT(reta_conf[idx].reta[pos] < priv->rxqs_n);
|
MLX5_ASSERT(reta_conf[idx].reta[pos] < priv->rxqs_n);
|
||||||
(*priv->reta_idx)[i] = reta_conf[idx].reta[pos];
|
(*priv->reta_idx)[i] = reta_conf[idx].reta[pos];
|
||||||
}
|
}
|
||||||
|
|
||||||
priv->skip_default_rss_reta = 1;
|
priv->skip_default_rss_reta = 1;
|
||||||
|
return mlx5_traffic_restart(dev);
|
||||||
if (dev->data->dev_started) {
|
|
||||||
mlx5_dev_stop(dev);
|
|
||||||
return mlx5_dev_start(dev);
|
|
||||||
}
|
|
||||||
return 0;
|
|
||||||
}
|
}
|
||||||
|
Loading…
Reference in New Issue
Block a user