patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Xueming(Steven) Li" <xuemingl@nvidia.com>
To: Slava Ovsiienko <viacheslavo@nvidia.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Cc: "bluca@debian.org" <bluca@debian.org>,
	"ktraynor@redhat.com" <ktraynor@redhat.com>
Subject: RE: [PATCH] net/mlx5/linux: fix missed Rx packet stats
Date: Fri, 12 Aug 2022 07:26:21 +0000	[thread overview]
Message-ID: <DM4PR12MB5373A0A2320D110B3E838F4EA1679@DM4PR12MB5373.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20220811053036.18924-1-viacheslavo@nvidia.com>

I know this patch targets 20.11 LTS, applied and thanks!

Please ping other maintainers if you want this patch in another LTS version. Usually, maintainers care the email subject with [19.11] or [21.11] prefix.

> -----Original Message-----
> From: Slava Ovsiienko <viacheslavo@nvidia.com>
> Sent: Thursday, August 11, 2022 1:31 PM
> To: stable@dpdk.org
> Cc: bluca@debian.org; ktraynor@redhat.com; Xueming(Steven) Li <xuemingl@nvidia.com>
> Subject: [PATCH] net/mlx5/linux: fix missed Rx packet stats
> 
> [ upstream commit 978a0303a3bf41598615a01392e6d4312101c3af ]
> 
> There was a typo - the device context was wrongly provided instead of counter's one for the DevX query operation.
> 
> Fixes: e6988afdc75a ("net/mlx5: fix imissed statistics")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> ---
>  drivers/net/mlx5/linux/mlx5_os.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/net/mlx5/linux/mlx5_os.c b/drivers/net/mlx5/linux/mlx5_os.c
> index f98cf90dd8..8bd717e6a9 100644
> --- a/drivers/net/mlx5/linux/mlx5_os.c
> +++ b/drivers/net/mlx5/linux/mlx5_os.c
> @@ -2589,8 +2589,8 @@ mlx5_os_read_dev_stat(struct mlx5_priv *priv, const char *ctr_name,
>  	if (priv->sh) {
>  		if (priv->q_counters != NULL &&
>  		    strcmp(ctr_name, "out_of_buffer") == 0)
> -			return mlx5_devx_cmd_queue_counter_query(priv->sh->ctx,
> -							   0, (uint32_t *)stat);
> +			return mlx5_devx_cmd_queue_counter_query
> +					(priv->q_counters, 0, (uint32_t *)stat);
>  		MKSTR(path, "%s/ports/%d/hw_counters/%s",
>  		      priv->sh->ibdev_path,
>  		      priv->dev_port,
> --
> 2.18.1


      reply	other threads:[~2022-08-12  7:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-11  5:30 Viacheslav Ovsiienko
2022-08-12  7:26 ` Xueming(Steven) Li [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=DM4PR12MB5373A0A2320D110B3E838F4EA1679@DM4PR12MB5373.namprd12.prod.outlook.com \
    --to=xuemingl@nvidia.com \
    --cc=bluca@debian.org \
    --cc=ktraynor@redhat.com \
    --cc=stable@dpdk.org \
    --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).