net/mlx5: reduce log level in hash list registration
authorMatan Azrad <matan@nvidia.com>
Mon, 23 Nov 2020 15:56:42 +0000 (15:56 +0000)
committerThomas Monjalon <thomas@monjalon.net>
Tue, 24 Nov 2020 22:30:21 +0000 (23:30 +0100)
In mlx5 internal hash list tool, there is a log print when an entry
allocation is failed: Can't allocate hash list entry.

Some initialization checks triggers hash list registration in order to
check some capabilities. Here, the failure in registration doesn't
lead to failure in the initialization flow, that is why the log level
can be lower.

Move the entry allocation failure log to debug level.

Signed-off-by: Matan Azrad <matan@nvidia.com>
Reviewed-by: Asaf Penso <asafp@nvidia.com>
Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
drivers/net/mlx5/mlx5_utils.c

index 9889437..848d108 100644 (file)
@@ -156,7 +156,7 @@ mlx5_hlist_register(struct mlx5_hlist *h, uint64_t key, void *ctx)
        entry = h->cb_create(h, key, ctx);
        if (!entry) {
                rte_errno = ENOMEM;
-               DRV_LOG(ERR, "Can't allocate hash list %s entry.", h->name);
+               DRV_LOG(DEBUG, "Can't allocate hash list %s entry.", h->name);
                goto done;
        }
        entry->key = key;