From: Thomas Monjalon Date: Wed, 30 Jan 2019 11:20:19 +0000 (+0100) Subject: doc: add references to flow isolated mode in NICs guide X-Git-Url: http://git.droids-corp.org/?a=commitdiff_plain;h=0e0fb9431cf351852f6c0f8ae9f46993c8461da5;p=dpdk.git doc: add references to flow isolated mode in NICs guide Some drivers (mlx, mvpp2, sfc) support the flow isolated mode, but the feature was not advertised. A reference to the feature description is added for each driver. Signed-off-by: Thomas Monjalon Acked-by: Shahaf Shuler --- diff --git a/doc/guides/nics/mlx4.rst b/doc/guides/nics/mlx4.rst index 4d4842cde5..4ad361a2c2 100644 --- a/doc/guides/nics/mlx4.rst +++ b/doc/guides/nics/mlx4.rst @@ -46,6 +46,8 @@ This capability allows the PMD to coexist with kernel network interfaces which remain functional, although they stop receiving unicast packets as long as they share the same MAC address. +The :ref:`flow_isolated_mode` is supported. + Compiling librte_pmd_mlx4 causes DPDK to be linked against libibverbs. Configuration diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst index af102f15a0..0b67496542 100644 --- a/doc/guides/nics/mlx5.rst +++ b/doc/guides/nics/mlx5.rst @@ -67,7 +67,7 @@ Features - Hardware checksum offloads. - Flow director (RTE_FDIR_MODE_PERFECT, RTE_FDIR_MODE_PERFECT_MAC_VLAN and RTE_ETH_FDIR_REJECT). -- Flow API. +- Flow API, including :ref:`flow_isolated_mode`. - Multiple process. - KVM and VMware ESX SR-IOV modes are supported. - RSS hash result is supported. diff --git a/doc/guides/nics/mvpp2.rst b/doc/guides/nics/mvpp2.rst index 9dcb93dd96..4101d2d89c 100644 --- a/doc/guides/nics/mvpp2.rst +++ b/doc/guides/nics/mvpp2.rst @@ -410,6 +410,9 @@ Flow API PPv2 offers packet classification capabilities via classifier engine which can be configured via generic flow API offered by DPDK. + +The :ref:`flow_isolated_mode` is supported. + For an additional description please refer to DPDK :doc:`../prog_guide/rte_flow`. Supported flow actions diff --git a/doc/guides/nics/sfc_efx.rst b/doc/guides/nics/sfc_efx.rst index 40065284bc..028c92cc3f 100644 --- a/doc/guides/nics/sfc_efx.rst +++ b/doc/guides/nics/sfc_efx.rst @@ -207,6 +207,8 @@ Supported actions: Validating flow rules depends on the firmware variant. +The :ref:`flow_isolated_mode` is supported. + Ethernet destinaton individual/group match ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte_flow.rst index 472dcef476..0203f4f61b 100644 --- a/doc/guides/prog_guide/rte_flow.rst +++ b/doc/guides/prog_guide/rte_flow.rst @@ -2557,8 +2557,10 @@ Return values: - 0 on success, a negative errno value otherwise and ``rte_errno`` is set. -Isolated mode -------------- +.. _flow_isolated_mode: + +Flow isolated mode +------------------ The general expectation for ingress traffic is that flow rules process it first; the remaining unmatched or pass-through traffic usually ends up in a