X-Git-Url: http://git.droids-corp.org/?a=blobdiff_plain;f=doc%2Fguides%2Fvdpadevs%2Fmlx5.rst;h=1f2ae6fb922fa4a352adf1604ba9a9e0b519da7e;hb=eb0e12c0c2991b3e12ee015db8f86355f38dcffc;hp=9a11eefd2cef4fb6cf8c3bc7ebf0e04dcc49282a;hpb=dde524d3ff3e75120f70872a998fd0d3de4dd09d;p=dpdk.git diff --git a/doc/guides/vdpadevs/mlx5.rst b/doc/guides/vdpadevs/mlx5.rst index 9a11eefd2c..1f2ae6fb92 100644 --- a/doc/guides/vdpadevs/mlx5.rst +++ b/doc/guides/vdpadevs/mlx5.rst @@ -7,7 +7,7 @@ MLX5 vDPA driver ================ The MLX5 vDPA (vhost data path acceleration) driver library -(**librte_pmd_mlx5_vdpa**) provides support for **Mellanox ConnectX-6**, +(**librte_vdpa_mlx5**) provides support for **Mellanox ConnectX-6**, **Mellanox ConnectX-6 Dx** and **Mellanox BlueField** families of 10/25/40/50/100/200 Gb/s adapters as well as their virtual functions (VF) in SR-IOV context. @@ -37,7 +37,7 @@ to get the best performances: - DevX allows to access firmware objects - Direct Rules manages flow steering at low-level hardware layer -Enabling librte_pmd_mlx5_vdpa causes DPDK applications to be linked against +Enabling librte_vdpa_mlx5 causes DPDK applications to be linked against libibverbs. A Mellanox mlx5 PCI device can be probed by either net/mlx5 driver or vdpa/mlx5 @@ -116,7 +116,7 @@ Driver options - 2, Completion queue scheduling will be managed by interrupts. Each CQ burst arms the CQ in order to get an interrupt event in the next traffic burst. - - Default mode is 0. + - Default mode is 1. - ``event_us`` parameter [int] @@ -125,8 +125,7 @@ Driver options - 0, A nonzero value to set timer step in micro-seconds. The timer thread dynamic delay change steps according to this value. Default value is 1us. - - 1, A nonzero value to set fixed timer delay in micro-seconds. Default value - is 100us. + - 1, A value to set fixed timer delay in micro-seconds. Default value is 0us. - ``no_traffic_time`` parameter [int] @@ -134,3 +133,40 @@ Driver options driver to no-traffic mode. In this mode the timer events are stopped and interrupts are configured to the device in order to notify traffic for the driver. Default value is 2s. + +- ``event_core`` parameter [int] + + CPU core number to set polling thread affinity to, default to control plane + cpu. + +- ``hw_latency_mode`` parameter [int] + + The completion queue moderation mode: + + - 0, HW default. + + - 1, Latency is counted from the first packet completion report. + + - 2, Latency is counted from the last packet completion. + +- ``hw_max_latency_us`` parameter [int] + + - 1 - 4095, The maximum time in microseconds that packet completion report + can be delayed. + + - 0, HW default. + +- ``hw_max_pending_comp`` parameter [int] + + - 1 - 65535, The maximum number of pending packets completions in an HW queue. + + - 0, HW default. + + +Error handling +^^^^^^^^^^^^^^ + +Upon potential hardware errors, mlx5 PMD try to recover, give up if failed 3 +times in 3 seconds, virtq will be put in disable state. User should check log +to get error information, or query vdpa statistics counter to know error type +and count report.