From: Shahaf Shuler <shahafs@mellanox.com>
To: yskoh@mellanox.com
Cc: xuemingl@mellanox.com, rasland@mellanox.com, dev@dpdk.org,
stable@dpdk.org
Subject: [dpdk-dev] [PATCH 2/3] net/mlx5: add representor specific statistics
Date: Mon, 8 Oct 2018 11:25:22 +0300 [thread overview]
Message-ID: <44fd5f67f73f583e694623abe05a83c2a5c346c0.1538986272.git.shahafs@mellanox.com> (raw)
In-Reply-To: <cover.1538986272.git.shahafs@mellanox.com>
Representor ports has a different set of extended statistics (as those are
logical ports which cannot count all that the PF can).
Cc: stable@dpdk.org
Cc: xuemingl@mellanox.com
Signed-off-by: Shahaf Shuler <shahafs@mellanox.com>
---
drivers/net/mlx5/mlx5_stats.c | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/drivers/net/mlx5/mlx5_stats.c b/drivers/net/mlx5/mlx5_stats.c
index 26e0a716f1..f1600342f8 100644
--- a/drivers/net/mlx5/mlx5_stats.c
+++ b/drivers/net/mlx5/mlx5_stats.c
@@ -107,6 +107,23 @@ static const struct mlx5_counter_ctrl mlx5_counters_init[] = {
.dpdk_name = "rx_bytes_phy",
.ctr_name = "rx_bytes_phy",
},
+ /* Representor only */
+ {
+ .dpdk_name = "rx_packets",
+ .ctr_name = "vport_rx_packets",
+ },
+ {
+ .dpdk_name = "rx_bytes",
+ .ctr_name = "vport_rx_bytes",
+ },
+ {
+ .dpdk_name = "tx_packets",
+ .ctr_name = "vport_tx_packets",
+ },
+ {
+ .dpdk_name = "tx_bytes",
+ .ctr_name = "vport_tx_bytes",
+ },
};
static const unsigned int xstats_n = RTE_DIM(mlx5_counters_init);
--
2.12.0
next prev parent reply other threads:[~2018-10-08 8:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 8:25 [dpdk-dev] [PATCH 0/3] Representor fixes for BlueField device Shahaf Shuler
2018-10-08 8:25 ` [dpdk-dev] [PATCH 1/3] net/mlx5: support missing counter in extended statistics Shahaf Shuler
2018-10-08 8:25 ` Shahaf Shuler [this message]
2018-10-08 8:25 ` [dpdk-dev] [PATCH 3/3] net/mlx5: always use representor ifindex for ioctl Shahaf Shuler
2018-10-11 4:56 ` [dpdk-dev] [PATCH 0/3] Representor fixes for BlueField device Shahaf Shuler
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=44fd5f67f73f583e694623abe05a83c2a5c346c0.1538986272.git.shahafs@mellanox.com \
--to=shahafs@mellanox.com \
--cc=dev@dpdk.org \
--cc=rasland@mellanox.com \
--cc=stable@dpdk.org \
--cc=xuemingl@mellanox.com \
--cc=yskoh@mellanox.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).