DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Alex Vesker <valex@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Slava Ovsiienko <viacheslavo@nvidia.com>, Matan Azrad <matan@nvidia.com>
Subject: RE: [PATCH v2] net/mlx5: add debug support for dumping all rte ports
Date: Wed, 4 Jan 2023 11:44:18 +0000	[thread overview]
Message-ID: <BYAPR12MB3078368F5E9D85E84CDB0125CFF59@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20221221101001.21255-1-valex@nvidia.com>

Hi,

> -----Original Message-----
> From: Alex Vesker <valex@nvidia.com>
> Sent: Wednesday, December 21, 2022 12:10 PM
> To: dev@dpdk.org
> Cc: Slava Ovsiienko <viacheslavo@nvidia.com>; Matan Azrad
> <matan@nvidia.com>; Raslan Darawsheh <rasland@nvidia.com>
> Subject: [PATCH v2] net/mlx5: add debug support for dumping all rte ports
> 
> Add a special value max_uint16 to request dump of all
> rte ethernet ports. This is useful for collecting the
> full info from all the ports in a single dump.
> 
> Signed-off-by: Alex Vesker <valex@nvidia.com>
> Reviewed-by: Ori Kam <orika@nvidia.com>
> ---
>  drivers/net/mlx5/linux/mlx5_socket.c | 39 ++++++++++++++++++----------
>  1 file changed, 26 insertions(+), 13 deletions(-)
> 
> v2: Fix iteration function to use only mlx5 devices
> 

Patch applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh

      parent reply	other threads:[~2023-01-04 11:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13  9:28 [PATCH] " Alex Vesker
2022-12-21 10:10 ` [PATCH v2] " Alex Vesker
2022-12-21 10:42   ` Slava Ovsiienko
2023-01-04 11:44   ` 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=BYAPR12MB3078368F5E9D85E84CDB0125CFF59@BYAPR12MB3078.namprd12.prod.outlook.com \
    --to=rasland@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=valex@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;
as well as URLs for NNTP newsgroup(s).