Hi,
On 27/04/2025 2:28 PM, Maayan Kashani wrote:
Queue sync operation was skipped on rule destroy.
Unlike on fw wqe rule create in which both fence and notify_hw
are set to true, on destroy fence was set to false causing
previous queue operation to be stuck in the queue forever.
Example:
rule_a - HW rule, rule_b - FW WQE rule.
Sequence:
rule_a destroy, burst=1 (HW rule put to queue but no DB)
rule_b destroy, burst=0 (FW WQE rule cmd but no queue sync)
Outcome:
rule_a is stuck forever in the queue - no completion.
Fixes: 338aaf911665 ("net/mlx5/hws: add send FW match STE using gen WQE")
Cc: sta...@dpdk.org
Signed-off-by: Alex Vesker <va...@nvidia.com>
Signed-off-by: Maayan Kashani <mkash...@nvidia.com>
---
Patch applied to next-net-mlx,
--
Kindest regards
Raslan Darawsheh
