From: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
To: Shahaf Shuler <shahafs@mellanox.com>
Cc: adrien.mazarguil@6wind.com, yskoh@mellanox.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 1/2] doc: update mlx5 statistics query
Date: Wed, 29 Nov 2017 13:14:29 +0100 [thread overview]
Message-ID: <20171129121429.5t3u7qbkpxz4jkp3@laranjeiro-vm.dev.6wind.com> (raw)
In-Reply-To: <20171129112908.29493-1-shahafs@mellanox.com>
On Wed, Nov 29, 2017 at 01:29:07PM +0200, Shahaf Shuler wrote:
> Update the guide with more details on the different statistics query
> possible with MLX5 PMD.
>
> Signed-off-by: Shahaf Shuler <shahafs@mellanox.com>
> ---
> doc/guides/nics/mlx5.rst | 13 +++++++++++--
> 1 file changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
> index f9558da89..154db64d7 100644
> --- a/doc/guides/nics/mlx5.rst
> +++ b/doc/guides/nics/mlx5.rst
> @@ -105,8 +105,6 @@ Limitations
> -----------
>
> - Inner RSS for VXLAN frames is not supported yet.
> -- Port statistics through software counters only. Flow statistics are
> - supported by hardware counters.
> - Hardware checksum RX offloads for VXLAN inner header are not supported yet.
> - Forked secondary process not supported.
> - Flow pattern without any specific vlan will match for vlan packets as well:
> @@ -134,6 +132,17 @@ Limitations
> to 0 are not supported.
> - VXLAN TSO and checksum offloads are not supported on VM.
>
> +Statistics
> +----------
> +
> +MLX5 supports various of methods to report statistics:
> +
> +Port statistics can be queried using ``rte_eth_stats_get()``. The port statistics are through SW only and counts the number of packets received or sent successfully by the PMD.
> +
> +Extended statistics can be queried using ``rte_eth_xstats_get()``. The extended statistics expose a wider set of counters counted by the device. The extended port statistics counts the number of packets received or sent successfully by the port. As Mellanox NICs are using the :ref:`Bifurcated Linux Driver <linux_gsg_linux_drivers>` those counters counts also packet received or sent by the Linux kernel. The counters with ``_phy`` suffix counts the total events on the physical port, therefore not valid for VF.
> +
> +Finally per-flow statistics can by queried using ``rte_flow_query`` when attaching a count action for specific flow. The flow counter counts the number of packets received successfully by the port and match the specific flow.
> +
> Configuration
> -------------
>
> --
> 2.12.0
For the series,
Acked-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
Thanks,
--
Nélio Laranjeiro
6WIND
next prev parent reply other threads:[~2017-11-29 12:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 11:29 Shahaf Shuler
2017-11-29 11:29 ` [dpdk-dev] [PATCH 2/2] net/mlx5: add physical port counters Shahaf Shuler
2017-11-29 12:14 ` Nelio Laranjeiro [this message]
2017-11-29 13:34 ` [dpdk-dev] [PATCH 1/2] doc: update mlx5 statistics query 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=20171129121429.5t3u7qbkpxz4jkp3@laranjeiro-vm.dev.6wind.com \
--to=nelio.laranjeiro@6wind.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=shahafs@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).