From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 974D9A053E; Mon, 3 Aug 2020 19:04:10 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 506F82BE1; Mon, 3 Aug 2020 19:04:09 +0200 (CEST) Received: from mellanox.co.il (mail-il-dmz.mellanox.com [193.47.165.129]) by dpdk.org (Postfix) with ESMTP id E917F11A2 for ; Mon, 3 Aug 2020 19:04:07 +0200 (CEST) Received: from Internal Mail-Server by MTLPINE1 (envelope-from dekelp@mellanox.com) with SMTP; 3 Aug 2020 20:04:03 +0300 Received: from mtl-vdi-280.wap.labs.mlnx. (mtl-vdi-280.wap.labs.mlnx [10.228.134.250]) by labmailer.mlnx (8.13.8/8.13.8) with ESMTP id 073H42hX022456; Mon, 3 Aug 2020 20:04:02 +0300 From: Dekel Peled To: ferruh.yigit@intel.com, arybchenko@solarflare.com, orika@mellanox.com, john.mcnamara@intel.com, marko.kovacevic@intel.com Cc: asafp@mellanox.com, matan@mellanox.com, elibr@mellanox.com, dev@dpdk.org Date: Mon, 3 Aug 2020 20:01:30 +0300 Message-Id: <33de39c7ef627b87f5e0bb34f364a92fffc39fc5.1596470130.git.dekelp@mellanox.com> X-Mailer: git-send-email 1.7.1 In-Reply-To: <5f9b4d30b81fa68ed875106785419a43cc7a6166.1590935677.git.dekelp@mellanox.com> References: <5f9b4d30b81fa68ed875106785419a43cc7a6166.1590935677.git.dekelp@mellanox.com> Subject: [dpdk-dev] [RFC v2] ethdev: add extensions attributes to IPv6 item 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" Using the current implementation of DPDK, an application cannot match on IPv6 packets, based on the existing extension headers, in a simple way. Field 'Next Header' in IPv6 header indicates type of the first extension header only. Following extension headers can't be identified by inspecting the IPv6 header. As a result, the existence or absence of specific extension headers can't be used for packet matching. For example, fragmented IPv6 packets contain a dedicated extension header, as detailed in RFC [1], which is not yet supported in rte_flow. Non-fragmented packets don't contain the fragment extension header. For an application to match on non-fragmented IPv6 packets, the current implementation doesn't provide a suitable solution. Matching on the Next Header field is not sufficient, since additional extension headers might be present in the same packet. To match on fragmented IPv6 packets, the same difficulty exists. Proposed update: A set of additional values will be added to IPv6 header struct. These values will indicate the existence of every defined extension header type, providing simple means for identification of existing extensions in the packet header. Continuing the above example, fragmented packets can be identified using the specific value indicating existence of fragment extension header. This update changes ABI, and is proposed for the 20.11 LTS version. [1] http://mails.dpdk.org/archives/dev/2020-March/160255.html Signed-off-by: Dekel Peled --- lib/librte_ethdev/rte_flow.h | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/lib/librte_ethdev/rte_flow.h b/lib/librte_ethdev/rte_flow.h index da8bfa5..8d2073d 100644 --- a/lib/librte_ethdev/rte_flow.h +++ b/lib/librte_ethdev/rte_flow.h @@ -792,11 +792,33 @@ struct rte_flow_item_ipv4 { * * Matches an IPv6 header. * + * Dedicated flags indicate existence of specific extension headers. + * * Note: IPv6 options are handled by dedicated pattern items, see * RTE_FLOW_ITEM_TYPE_IPV6_EXT. */ struct rte_flow_item_ipv6 { struct rte_ipv6_hdr hdr; /**< IPv6 header definition. */ + uint64_t hop_ext_exist:1; + /**< Hop-by-Hop Options extension header exists. */ + uint64_t rout_ext_exist:1; + /**< Routing extension header exists. */ + uint64_t frag_ext_exist:1; + /**< Fragment extension header exists. */ + uint64_t auth_ext_exist:1; + /**< Authentication extension header exists. */ + uint64_t esp_ext_exist:1; + /**< Encapsulation Security Payload extension header exists. */ + uint64_t dest_ext_exist:1; + /**< Destination Options extension header exists. */ + uint64_t mobil_ext_exist:1; + /**< Mobility extension header exists. */ + uint64_t hip_ext_exist:1; + /**< Host Identity Protocol extension header exists. */ + uint64_t shim6_ext_exist:1; + /**< Shim6 Protocol extension header exists. */ + uint64_t reserved:55; + /**< Reserved for future extension headers, must be zero. */ }; /** Default mask for RTE_FLOW_ITEM_TYPE_IPV6. */ -- 1.8.3.1