From: Slava Ovsiienko <viacheslavo@mellanox.com>
To: Shy Shyman <shys@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] net/mlx5: fix file path location of HW counters
Date: Wed, 15 Jul 2020 10:54:28 +0000 [thread overview]
Message-ID: <AM4PR05MB32653DAE45E71AF0C302C044D27E0@AM4PR05MB3265.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20200715105055.80089-1-shys@mellanox.com>
> -----Original Message-----
> From: Shy Shyman <shys@mellanox.com>
> Sent: Wednesday, July 15, 2020 13:51
> To: dev@dpdk.org
> Cc: Slava Ovsiienko <viacheslavo@mellanox.com>; stable@dpdk.org
> Subject: [PATCH] net/mlx5: fix file path location of HW counters
>
> When debugging performance of a DPDK application the user may need to
> view the different statistics of DPDK(for example out_of_buffer) This can be
> enabled by using testpmd command 'show port xstats <port_id>' for
> example.
>
> The current implementation assumes legacy mode in which the counters are
> at <ibdev_path>/<port_id>/hw_counters/<file_name>.
> In switchdev mode the counters file is located right after the device name,
> hence resides at <ibdev_path>/hw_counters.
>
> The fix tries to open the path in the second location after a failure to open
> the file from the first location.
>
> Fixes: 9c0a9eed37f1 ("net/mlx5: switch to the names in the shared IB
> context")
>
> Cc: stable@dpdk.org
> Cc: viacheslavo@mellanox.com
>
> Signed-off-by: Shy Shyman <shys@mellanox.com>
Acked-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
next prev parent reply other threads:[~2020-07-15 10:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 10:50 Shy Shyman
2020-07-15 10:54 ` Slava Ovsiienko [this message]
2020-07-20 7:20 ` [dpdk-stable] [dpdk-dev] " Raslan Darawsheh
-- strict thread matches above, loose matches on Subject: below --
2020-07-15 10:40 [dpdk-stable] " Shy Shyman
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=AM4PR05MB32653DAE45E71AF0C302C044D27E0@AM4PR05MB3265.eurprd05.prod.outlook.com \
--to=viacheslavo@mellanox.com \
--cc=dev@dpdk.org \
--cc=shys@mellanox.com \
--cc=stable@dpdk.org \
/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).