common/mlx5: fix UAR allocation diagnostics messages

Depending on kernel capabilities and rdma-core version the mapping of
UAR (User Access Region) of desired memory caching type (non-cached or
write combining) might fail. The PMD implements the flexible strategy
of UAR mapping, alternating the type of caching to succeed.

During this process the failure diagnostics messages are emitted.
These messages are merely diagnostics ones and the logging level should
be adjusted to DEBUG.

Fixes: 9cc0e99c81ab0 ("common/mlx5: share UAR allocation routine")
Cc: stable@dpdk.org
Signed-off-by: Michael Baum <michaelba@nvidia.com>
Reviewed-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Acked-by: Matan Azrad <matan@nvidia.com>

diff --git a/drivers/common/mlx5/mlx5_common.c b/drivers/common/mlx5/mlx5_common.c
index e8603c7ea9822d6bb88ef03c905b800db2c8e266..e3497c40ebd1bdfa8b436f37d95bef623ea50f66 100644 (file)
--- a/drivers/common/mlx5/mlx5_common.c
+++ b/drivers/common/mlx5/mlx5_common.c
@@ -977,7 +977,7 @@ mlx5_devx_alloc_uar(void *ctx, int mapping)
                         * If Verbs/kernel does not support "Non-Cached"
                         * try the "Write-Combining".
                         */
-                       DRV_LOG(WARNING, "Failed to allocate DevX UAR (NC)");
+                       DRV_LOG(DEBUG, "Failed to allocate DevX UAR (NC)");
                        uar_mapping = MLX5DV_UAR_ALLOC_TYPE_BF;
                        uar = mlx5_glue->devx_alloc_uar(ctx, uar_mapping);
                }
@@ -995,7 +995,7 @@ mlx5_devx_alloc_uar(void *ctx, int mapping)
                 * IB device context, on context closure all UARs
                 * will be freed, should be no memory/object leakage.
                 */
-               DRV_LOG(WARNING, "Retrying to allocate DevX UAR");
+               DRV_LOG(DEBUG, "Retrying to allocate DevX UAR");
                uar = NULL;
        }
        /* Check whether we finally succeeded with valid UAR allocation. */