From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <dev-bounces@dpdk.org> Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 7635AA0C3F; Mon, 29 Mar 2021 18:52:49 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 08B17140D97; Mon, 29 Mar 2021 18:52:49 +0200 (CEST) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) by mails.dpdk.org (Postfix) with ESMTP id 64A22406FF for <dev@dpdk.org>; Mon, 29 Mar 2021 18:52:47 +0200 (CEST) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id 0690117ED; Mon, 29 Mar 2021 12:52:45 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Mon, 29 Mar 2021 12:52:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; s=fm3; bh=o/qA8elHrlOsgsrcs0jNvFJRvk Hw9d1tL3C6Y7oM5LU=; b=hU6c95b5THBQVUzK9o9Umb3PWeTyw/LFHVqdn2Ry/V f8AQ26rcFRVz/MYHJzJycPBGJI/OW5LHyGpw0Gqhrkexg7mqrbq+aCfuFYogQhaP 0cOD4V0dlOE2DvY4PZSbUvymmSikkABA/cWx5xN0hd+kRfnmrjGG57FD7nxzWGUL bHcKfnOF/oWvP3CWVAOeQRYLmwfkk9bxT/D4l1AlitDhau9TPT8cDfJuYYleDimC RHbsIRnKgmdIP6hWaphexpt1jTib/5SeuJoW2zNRiHCAEvwMX6ZZNNsUS9UeObnm ns6XtADSy78ZPULKku9+H2VCJvKzC2aJa4skJrLy37Gw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:date:from :message-id:mime-version:subject:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=o/qA8elHrlOsgsrcs 0jNvFJRvkHw9d1tL3C6Y7oM5LU=; b=R4uLxj133Dw8PJj8KAeYrYSq7Sj/ldBmb Cfn3jsp58EfP6Q1PCR6wdGAvVY8fbw0INVzVwYrrLV/EJtdueGBhlQ9UOgSrrPIJ EZyI85kc+PGAHHpVlY3VrojPN6ubedoOzXpbL+wZS11zJWZSte5QnIx6AFRm7afS KvlSLhGZ5DrXKmtyndzsKptuVW2nYFJ1+RYYrBO+bAkyS8dXPsPwRwBWQRDUhi2H 3Kpmq/xVGpSDukvDzCwowHBA3Vx7FeeYTfDTfTomV+8nSaLD0h6sF+kg6iqQYrAX X+HmXdV45BQWG2l46051rikBSKHZhggqypwh8zDMZkLX0N86Nz0dQ== X-ME-Sender: <xms:3AViYAD2OEgi4FnaoBXgpkHKj3Pn_TLZgcLhoodIql_e_c9VEU7Bww> <xme:3AViYBD8ypQ4p3YexYtUaeqVZRhzTL5ZLpb7mHiwooIFNGJTzM1FS_LlhGwFJykcU V1lGq0lQqOa7yWLAA> X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudehkedguddtjecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefhvffufffkofgggfestdekredtredttdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucggtf frrghtthgvrhhnpefgleffhfegffejudegkefgtdeggffhgeejfeetffeulefffefgfeeg iefhgffhfeenucffohhmrghinhepohhpvghnnhgvthifohhrkhhinhhgrdhorhhgnecukf hppeejjedrudefgedrvddtfedrudekgeenucevlhhushhtvghrufhiiigvpedtnecurfgr rhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: <xmx:3AViYKbOn20QPRlSS6YF2gWC9tf3IsEsZH5W7vBKNTJoaM1Fk1iJPQ> <xmx:3AViYGxsIodbrRm9dxDq8xm4MURk0jld1xsQNpXDE--c11v2pUkkug> <xmx:3AViYNdvoOIoiv8ZAUx92ZMonSbrLQ3zaCpEKHaNLyQYBx1vL79qbA> <xmx:3QViYE-Ry0j2hezwzP9w-9MihTYRbylUaiVVsVPDSZ_dSrEacH63Ag> Received: from xps.monjalon.net (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 8B73E1080054; Mon, 29 Mar 2021 12:52:44 -0400 (EDT) From: Thomas Monjalon <thomas@monjalon.net> To: dev@dpdk.org Cc: Ori Kam <orika@nvidia.com> Date: Mon, 29 Mar 2021 18:52:14 +0200 Message-Id: <20210329165214.668793-1-thomas@monjalon.net> X-Mailer: git-send-email 2.30.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [dpdk-dev] [PATCH] doc: remove obsolete future considerations in flow guide X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org Sender: "dev" <dev-bounces@dpdk.org> After 4 years, rte_flow has evolved enough to not require special notes about what could be added in future. Part of the removed plans were obsolete anyway. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> --- doc/guides/prog_guide/rte_flow.rst | 38 +----------------------------- 1 file changed, 1 insertion(+), 37 deletions(-) diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte_flow.rst index 62a57919eb..c6cef43bdd 100644 --- a/doc/guides/prog_guide/rte_flow.rst +++ b/doc/guides/prog_guide/rte_flow.rst @@ -719,9 +719,6 @@ Most of these are basically protocol header definitions with associated bit-masks. They must be specified (stacked) from lowest to highest protocol layer to form a matching pattern. -The following list is not exhaustive, new protocols will be added in the -future. - Item: ``ANY`` ^^^^^^^^^^^^^ @@ -1523,8 +1520,7 @@ that VOID is ignored. Action types ~~~~~~~~~~~~ -Common action types are described in this section. Like pattern item types, -this list is not exhaustive as new actions will be added in the future. +Common action types are described in this section. Action: ``END`` ^^^^^^^^^^^^^^^ @@ -2854,19 +2850,6 @@ A method to generate them remains to be defined. Application may use PMD dynamic items or actions in flow rules. In that case size of configuration object in dynamic element must be a pointer size. -Planned types -~~~~~~~~~~~~~ - -Pattern item types will be added as new protocols are implemented. - -Variable headers support through dedicated pattern items, for example in -order to match specific IPv4 options and IPv6 extension headers would be -stacked after IPv4/IPv6 items. - -Other action types are planned but are not defined yet. These include the -ability to alter packet data in several ways, such as performing -encapsulation/decapsulation of tunnel headers. - Rules management ---------------- @@ -3361,8 +3344,6 @@ so the API level protection is disabled. Please note that this API-level mutex protects only rte_flow functions, other control path functions are not in scope. -More will be added over time. - Device compatibility -------------------- @@ -3511,22 +3492,5 @@ PMDs. - In order to save priority levels, PMDs may evaluate whether rules are likely to collide and adjust their priority accordingly. -Future evolutions ------------------ - -- A device profile selection function which could be used to force a - permanent profile instead of relying on its automatic configuration based - on existing flow rules. - -- A method to optimize *rte_flow* rules with specific pattern items and - action types generated on the fly by PMDs. DPDK should assign negative - numbers to these in order to not collide with the existing types. See - `Negative types`_. - -- Adding specific egress pattern items and actions as described in - `Attribute: Traffic direction`_. - -- Optional software fallback when PMDs are unable to handle requested flow - rules so applications do not have to implement their own. .. _OpenFlow Switch Specification: https://www.opennetworking.org/software-defined-standards/specifications/ -- 2.30.1