DPDK patches and discussions
 help / color / mirror / Atom feed
From: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
To: dev@dpdk.org
Cc: rasland@nvidia.com, matan@nvidia.com, orika@nvidia.com,
	thomas@monjalon.net, iryzhov@nfware.com
Subject: [dpdk-dev] [PATCH] net/mlx5: make Tx scheduling xstats names compliant
Date: Thu, 19 Nov 2020 19:18:24 +0000	[thread overview]
Message-ID: <1605813504-19746-1-git-send-email-viacheslavo@nvidia.com> (raw)

xstats names for Tx packet scheduling should be compliant with [1]

[1] http://doc.dpdk.org/guides/prog_guide/poll_mode_drv.html?highlight=xstats#extended-statistics-api

Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
---
 drivers/net/mlx5/mlx5_txpp.c | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/drivers/net/mlx5/mlx5_txpp.c b/drivers/net/mlx5/mlx5_txpp.c
index 8aad92f..2438bf1 100644
--- a/drivers/net/mlx5/mlx5_txpp.c
+++ b/drivers/net/mlx5/mlx5_txpp.c
@@ -19,14 +19,14 @@
 #include "mlx5_common_os.h"
 
 static const char * const mlx5_txpp_stat_names[] = {
-	"txpp_err_miss_int", /* Missed service interrupt. */
-	"txpp_err_rearm_queue",	/* Rearm Queue errors. */
-	"txpp_err_clock_queue", /* Clock Queue errors. */
-	"txpp_err_ts_past", /* Timestamp in the past. */
-	"txpp_err_ts_future", /* Timestamp in the distant future. */
-	"txpp_jitter", /* Timestamp jitter (one Clock Queue completion). */
-	"txpp_wander", /* Timestamp jitter (half of Clock Queue completions). */
-	"txpp_sync_lost", /* Scheduling synchronization lost. */
+	"tx_pp_missed_interrupt_errors", /* Missed service interrupt. */
+	"tx_pp_rearm_queue_errors", /* Rearm Queue errors. */
+	"tx_pp_clock_queue_errors", /* Clock Queue errors. */
+	"tx_pp_timestamp_past_errors", /* Timestamp in the past. */
+	"tx_pp_timestamp_future_errors", /* Timestamp in the distant future. */
+	"tx_pp_jitter", /* Timestamp jitter (one Clock Queue completion). */
+	"tx_pp_wander", /* Timestamp wander (half of Clock Queue CQEs). */
+	"tx_pp_sync_lost", /* Scheduling synchronization lost. */
 };
 
 /* Destroy Event Queue Notification Channel. */
-- 
1.8.3.1


             reply	other threads:[~2020-11-19 19:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-19 19:18 Viacheslav Ovsiienko [this message]
2020-11-22 12:59 ` 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=1605813504-19746-1-git-send-email-viacheslavo@nvidia.com \
    --to=viacheslavo@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=iryzhov@nfware.com \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=thomas@monjalon.net \
    /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).