OSDN Git Service

net/mlx5: Reduce No CQ found log level from warn to debug
authorParav Pandit <parav@mellanox.com>
Thu, 5 Dec 2019 22:06:20 +0000 (16:06 -0600)
committerSaeed Mahameed <saeedm@mellanox.com>
Tue, 7 Jan 2020 18:41:17 +0000 (10:41 -0800)
commit7396ae3d1cfe05be42e5f6b1883c9ed594cc42ba
treef7c5aa79dfe76a50449770661ecd86a0be682de6
parent57c7fce14b1ad512a42abe33cb721a2ea3520d4b
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: Parav Pandit <parav@mellanox.com>
Signed-off-by: Saeed Mahameed <saeedm@mellanox.com>
drivers/net/ethernet/mellanox/mlx5/core/eq.c