Commit 7396ae3d authored by Parav Pandit's avatar Parav Pandit Committed by Saeed Mahameed

net/mlx5: Reduce No CQ found log level from warn to debug

In below sequence, a EQE entry arrives for a CQ which is on the path of
being destroyed.

           cpu-0               cpu-1
           ------              -----
mlx5_core_destroy_cq()      mlx5_eq_comp_int()
  mlx5_eq_del_cq()          [..]
    radix_tree_delete()     [..]
  [..]                         mlx5_eq_cq_get() /* Didn't find CQ is
                                                 * a valid case.
                                                 */
  /* destroy CQ in hw */
  mlx5_cmd_exec()

This is still a valid scenario and correct delete CQ sequence, as
mirror of the CQ create sequence.
Hence, suppress the non harmful debug message from warn to debug level.
Keep the debug log message rate limited because user application can
trigger it repeatedly.
Signed-off-by: default avatarParav Pandit <parav@mellanox.com>
Signed-off-by: default avatarSaeed Mahameed <saeedm@mellanox.com>
parent 57c7fce1
...@@ -156,7 +156,8 @@ static int mlx5_eq_comp_int(struct notifier_block *nb, ...@@ -156,7 +156,8 @@ static int mlx5_eq_comp_int(struct notifier_block *nb,
cq->comp(cq, eqe); cq->comp(cq, eqe);
mlx5_cq_put(cq); mlx5_cq_put(cq);
} else { } else {
mlx5_core_warn(eq->dev, "Completion event for bogus CQ 0x%x\n", cqn); dev_dbg_ratelimited(eq->dev->device,
"Completion event for bogus CQ 0x%x\n", cqn);
} }
++eq->cons_index; ++eq->cons_index;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment