From: Shahaf Shuler Date: Wed, 29 Nov 2017 11:29:07 +0000 (+0200) Subject: doc: update mlx5 statistics query X-Git-Tag: spdx-start~621 X-Git-Url: http://git.droids-corp.org/?a=commitdiff_plain;h=abdb903faccb684f5c981ef4d93d5f89ae75b854;p=dpdk.git doc: update mlx5 statistics query Update the guide with more details on the different statistics query possible with MLX5 PMD. Signed-off-by: Shahaf Shuler Acked-by: Nelio Laranjeiro --- diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst index f9558da89b..154db64d7b 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 ` 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 -------------