From patchwork Wed Jan 30 11:20:19 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Thomas Monjalon X-Patchwork-Id: 50092 X-Patchwork-Delegate: thomas@monjalon.net Return-Path: X-Original-To: patchwork@dpdk.org Delivered-To: patchwork@dpdk.org Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 5C1701B396; Wed, 30 Jan 2019 12:20:53 +0100 (CET) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 0B5E11B395 for ; Wed, 30 Jan 2019 12:20:52 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 79C02221B2; Wed, 30 Jan 2019 06:20:51 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 30 Jan 2019 06:20:51 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; s=mesmtp; bh=jV6/ZDvIaI zwAxpaUe9+Voo15/B+fFG8mRrK86MgUlA=; b=gHQkCd8clW73mmHHfP7/e4nit7 ve3DhUhleuBdv7c6AY0x4FF5POm5Cc21VspJKsx1tn7oaobeymM9QwmqvkFDn4fA S8nkc4FK6U1radk0INYIoHvCgORvlBVCzxuKcUhjHT98BwLXbBtGp5dPM68n4Y8e o0jofPQD31++TAWmA= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:date:from :in-reply-to:message-id:mime-version:references:subject:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=jV6/ZDvIaIzwAxpaUe9+Voo15/B+fFG8mRrK86MgUlA=; b=M9/GDcU0 hJC0aH70L77PV6XbCvnP3fet9tQX5TUhbM4Ksy9vbHSqiv/ec0cEZiuQ0KY+lkgp YIvgDMBkjlbPx6r5mEg54WN7u7Ps++jsuZi1eJxUwU85fxcNsqM8lEm3XPoPQt6E XEODfOnjC3jiOQGNYIUIX2sYkQUkVPoRiYvfXhHuWlVKGIhr4TdCn+oV7+anBIAj 9Pg0jXmaDM2/Tia7teUzWnwryCFPL/w1SmxGBE4WAKBC1sIRJQ8IqpzyzPLmz0Zl e0B7dNmNbRmc4/0txkF93ToQmuQx0Jnli2VRoqt00u9U4T5ppZz/qYfRm4AzvXsS 8Yql5rGCTazlRQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrjeeggddviecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecufedt tdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhephffvufffkffojg hfggfgsedtkeertdertddtnecuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceo thhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukfhppeejjedrudefgedrvddtfe drudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhho nhdrnhgvthenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from xps.monjalon.net (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id E7C1EE412E; Wed, 30 Jan 2019 06:20:49 -0500 (EST) From: Thomas Monjalon To: john.mcnamara@intel.com, marko.kovacevic@intel.com, shahafs@mellanox.com, yskoh@mellanox.com, Matan Azrad , Tomasz Duszynski , Dmitri Epshtein , Natalie Samsonov , Andrew Rybchenko , Adrien Mazarguil Cc: dev@dpdk.org Date: Wed, 30 Jan 2019 12:20:19 +0100 Message-Id: <20190130112020.871-3-thomas@monjalon.net> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20190130112020.871-1-thomas@monjalon.net> References: <20190130112020.871-1-thomas@monjalon.net> MIME-Version: 1.0 Subject: [dpdk-dev] [PATCH 2/3] doc: add references to flow isolated mode in NICs guide X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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 --- doc/guides/nics/mlx4.rst | 2 ++ doc/guides/nics/mlx5.rst | 2 +- doc/guides/nics/mvpp2.rst | 3 +++ doc/guides/nics/sfc_efx.rst | 2 ++ doc/guides/prog_guide/rte_flow.rst | 6 ++++-- 5 files changed, 12 insertions(+), 3 deletions(-) diff --git a/doc/guides/nics/mlx4.rst b/doc/guides/nics/mlx4.rst index 4d4842cde..4ad361a2c 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 3f168b161..aa3a884b9 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 9dcb93dd9..4101d2d89 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 40065284b..028c92cc3 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 472dcef47..0203f4f61 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