DPDK patches and discussions
 help / color / mirror / Atom feed
From: Yongseok Koh <yskoh@mellanox.com>
To: "Xueming(Steven) Li" <xuemingl@mellanox.com>
Cc: Shahaf Shuler <shahafs@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] net/mlx5: fix representor port xstats
Date: Fri, 14 Sep 2018 16:50:43 +0000	[thread overview]
Message-ID: <CBD4EF0C-FB2B-47D5-B3AA-94E19C087D26@mellanox.com> (raw)
In-Reply-To: <1536906807-118827-1-git-send-email-xuemingl@mellanox.com>


> On Sep 13, 2018, at 11:33 PM, Xueming Li <xuemingl@mellanox.com> wrote:
> 
> This patch fixes the issue that representor port shows xstats of PF.
> 
> Fixes: 5a4b8e2612c5 ("net/mlx5: probe all port representors")

Wrong commit SHA.

> Signed-off-by: Xueming Li <xuemingl@mellanox.com>
> ---
> drivers/net/mlx5/mlx5_stats.c | 13 +++++++++----
> 1 file changed, 9 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/net/mlx5/mlx5_stats.c b/drivers/net/mlx5/mlx5_stats.c
> index 91f3d47..ed5b51b 100644
> --- a/drivers/net/mlx5/mlx5_stats.c
> +++ b/drivers/net/mlx5/mlx5_stats.c
> @@ -146,7 +146,7 @@ struct mlx5_counter_ctrl {
> 	et_stats->cmd = ETHTOOL_GSTATS;
> 	et_stats->n_stats = xstats_ctrl->stats_n;
> 	ifr.ifr_data = (caddr_t)et_stats;
> -	ret = mlx5_ifreq(dev, SIOCETHTOOL, &ifr, 1);
> +	ret = mlx5_ifreq(dev, SIOCETHTOOL, &ifr, 0);
> 	if (ret) {
> 		DRV_LOG(WARNING,
> 			"port %u unable to read statistic values from device",
> @@ -194,7 +194,7 @@ struct mlx5_counter_ctrl {
> 
> 	drvinfo.cmd = ETHTOOL_GDRVINFO;
> 	ifr.ifr_data = (caddr_t)&drvinfo;
> -	ret = mlx5_ifreq(dev, SIOCETHTOOL, &ifr, 1);
> +	ret = mlx5_ifreq(dev, SIOCETHTOOL, &ifr, 0);
> 	if (ret) {
> 		DRV_LOG(WARNING, "port %u unable to query number of statistics",
> 			dev->data->port_id);
> @@ -229,7 +229,6 @@ struct mlx5_counter_ctrl {
> 		return;
> 	}
> 	dev_stats_n = ret;
> -	xstats_ctrl->stats_n = dev_stats_n;
> 	/* Allocate memory to grab stat names and values. */
> 	str_sz = dev_stats_n * ETH_GSTRING_LEN;
> 	strings = (struct ethtool_gstrings *)
> @@ -244,7 +243,7 @@ struct mlx5_counter_ctrl {
> 	strings->string_set = ETH_SS_STATS;
> 	strings->len = dev_stats_n;
> 	ifr.ifr_data = (caddr_t)strings;
> -	ret = mlx5_ifreq(dev, SIOCETHTOOL, &ifr, 1);
> +	ret = mlx5_ifreq(dev, SIOCETHTOOL, &ifr, 0);
> 	if (ret) {
> 		DRV_LOG(WARNING, "port %u unable to get statistic names",
> 			dev->data->port_id);
> @@ -275,6 +274,7 @@ struct mlx5_counter_ctrl {
> 			goto free;
> 		}
> 	}
> +	xstats_ctrl->stats_n = dev_stats_n;

Any reason to move it?
If it is done to group the code, I'm fine with that.

Thanks,
Yongseok

> 	/* Copy to base at first time. */
> 	assert(xstats_n <= MLX5_MAX_XSTATS);
> 	ret = mlx5_read_dev_counters(dev, xstats_ctrl->base);
> @@ -307,6 +307,8 @@ struct mlx5_counter_ctrl {
> 	unsigned int i;
> 	uint64_t counters[n];
> 
> +	if (!priv->xstats_ctrl.stats_n)
> +		return 0;
> 	if (n >= xstats_n && stats) {
> 		struct mlx5_xstats_ctrl *xstats_ctrl = &priv->xstats_ctrl;
> 		int stats_n;
> @@ -480,8 +482,11 @@ struct mlx5_counter_ctrl {
> mlx5_xstats_get_names(struct rte_eth_dev *dev __rte_unused,
> 		      struct rte_eth_xstat_name *xstats_names, unsigned int n)
> {
> +	struct priv *priv = dev->data->dev_private;
> 	unsigned int i;
> 
> +	if (!priv->xstats_ctrl.stats_n)
> +		return 0;
> 	if (n >= xstats_n && xstats_names) {
> 		for (i = 0; i != xstats_n; ++i) {
> 			strncpy(xstats_names[i].name,
> -- 
> 1.8.3.1
> 

  reply	other threads:[~2018-09-14 16:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-06 10:28 [dpdk-dev] [PATCH] " Xueming Li
2018-09-14  6:33 ` [dpdk-dev] [PATCH v2] " Xueming Li
2018-09-14 16:50   ` Yongseok Koh [this message]
2018-09-15  5:20     ` Xueming(Steven) Li
2018-09-19  7:55   ` [dpdk-dev] [PATCH v3] " Xueming Li
2018-09-28  0:11     ` Yongseok Koh
2018-10-04 20:46       ` Thomas Monjalon

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=CBD4EF0C-FB2B-47D5-B3AA-94E19C087D26@mellanox.com \
    --to=yskoh@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=shahafs@mellanox.com \
    --cc=xuemingl@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).