From: Raslan Darawsheh <rasland@nvidia.com>
To: Dariusz Sosnowski <dsosnowski@nvidia.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>,
Matan Azrad <matan@nvidia.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH 0/2] net/mlx5: small debugging improvements
Date: Wed, 25 Mar 2026 16:28:46 +0200 [thread overview]
Message-ID: <e468a4fd-4e3b-45be-a593-a030e5fe74ba@nvidia.com> (raw)
In-Reply-To: <20260324171028.26727-1-dsosnowski@nvidia.com>
Hi,
On 24/03/2026 7:10 PM, Dariusz Sosnowski wrote:
> Small debugging improvements for mlx5 PMD:
>
> - Fix error logs generated on failure to modify SQ and RQ,
> so that verbose FW error is printed.
> - Add reporting share group and share queue ID
> in mlx5 implementation of rte_eth_rx_queue_info_get().
>
> Dariusz Sosnowski (2):
> common/mlx5: fix error logging for queue modify
> net/mlx5: report share group and queue ID
>
> drivers/common/mlx5/mlx5_devx_cmds.c | 19 ++++++++-----------
> drivers/net/mlx5/mlx5_rx.c | 4 ++++
> 2 files changed, 12 insertions(+), 11 deletions(-)
>
> --
> 2.47.3
>
Series applied to next-net-mlx,
Kindest regards
Raslan Darawsheh
prev parent reply other threads:[~2026-03-25 14:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 17:10 [PATCH 0/2] net/mlx5: small debugging improvements Dariusz Sosnowski
2026-03-24 17:10 ` [PATCH 1/2] common/mlx5: fix error logging for queue modify Dariusz Sosnowski
2026-03-24 17:10 ` [PATCH 2/2] net/mlx5: report share group and queue ID Dariusz Sosnowski
2026-03-25 14:28 ` Raslan Darawsheh [this message]
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=e468a4fd-4e3b-45be-a593-a030e5fe74ba@nvidia.com \
--to=rasland@nvidia.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=suanmingm@nvidia.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox