From: Thomas Monjalon <thomas@monjalon.net>
To: Gregory Etelson <getelson@nvidia.com>
Cc: dev@dpdk.org, stable@dpdk.org, matan@nvidia.com,
rasland@nvidia.com, stable@dpdk.org,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Subject: Re: [PATCH v2] common/mlx5: update DevX error logging
Date: Fri, 08 Jul 2022 16:23:45 +0200 [thread overview]
Message-ID: <3085347.4MS8fQxZnU@thomas> (raw)
In-Reply-To: <20220706140236.16887-1-getelson@nvidia.com>
06/07/2022 16:02, Gregory Etelson:
> Current PMD logs all DevX errors at error level.
>
> DevX interface can fail queue counters allocation on some hardware
> types. That is a known issue.
> PMD fallback to VERB API to allocate queue counters
> when it detects the fault.
> That DevX failure should not be logged as PMD error.
>
> The patch provides DevX with flexible API that selects log level.
>
> cc: stable@dpdk.org
Why is there this cc line?
> Signed-off-by: Gregory Etelson <getelson@nvidia.com>
> Acked-by: Matan Azrad <matan@nvidia.com>
next prev parent reply other threads:[~2022-07-08 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 14:48 [PATCH] common/mlx5: update DevX error logging Gregory Etelson
2022-07-06 14:02 ` [PATCH v2] " Gregory Etelson
2022-07-08 14:23 ` Thomas Monjalon [this message]
2022-07-10 16:02 ` [PATCH v3] " Gregory Etelson
2022-08-14 13:51 ` Raslan Darawsheh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3085347.4MS8fQxZnU@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=getelson@nvidia.com \
--cc=matan@nvidia.com \
--cc=rasland@nvidia.com \
--cc=stable@dpdk.org \
--cc=viacheslavo@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.