DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Rongwei Liu <rongweil@nvidia.com>, Matan Azrad <matan@nvidia.com>,
	Slava Ovsiienko <viacheslavo@nvidia.com>,
	Ori Kam <orika@nvidia.com>,
	"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH v1] net/mlx5: add Rx drop counters to xstats
Date: Sun, 29 May 2022 13:34:00 +0000	[thread overview]
Message-ID: <BYAPR12MB307884A0019B16DD5899FC74CFDA9@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20220526024941.1296966-1-rongweil@nvidia.com>

Hi,

> -----Original Message-----
> From: Rongwei Liu <rongweil@nvidia.com>
> Sent: Thursday, May 26, 2022 5:50 AM
> To: Matan Azrad <matan@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Ori Kam <orika@nvidia.com>; NBU-Contact-
> Thomas Monjalon (EXTERNAL) <thomas@monjalon.net>
> Cc: dev@dpdk.org; Raslan Darawsheh <rasland@nvidia.com>
> Subject: [PATCH v1] net/mlx5: add Rx drop counters to xstats
> 
> Add two kinds of Rx drop counters to DPDK xstats which are physical port
> scope.
> 
> 1. rx_prio[0-7]_buf_discard
>    The number of unicast packets dropped due to lack of shared
>    buffer resources.
> 2. rx_prio[0-7]_cong_discard
>    The number of packets that is dropped by the Weighted Random
>    Early Detection (WRED) function.
> 
> Prio[0-7] is determined by VLAN PCP value which is 0 by default.
> Both counters are retrieved from kernel ethtool API which calls PRM
> command finally.
> 
> Signed-off-by: Rongwei Liu <rongweil@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>

Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh

      reply	other threads:[~2022-05-29 13:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-26  2:49 Rongwei Liu
2022-05-29 13:34 ` 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=BYAPR12MB307884A0019B16DD5899FC74CFDA9@BYAPR12MB3078.namprd12.prod.outlook.com \
    --to=rasland@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=rongweil@nvidia.com \
    --cc=thomas@monjalon.net \
    --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).