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 3EE6FA04E7; Sun, 15 Nov 2020 15:07:45 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id E0D7F4C97; Sun, 15 Nov 2020 15:07:42 +0100 (CET) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id F2FF7493D for ; Sun, 15 Nov 2020 15:07:41 +0100 (CET) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 463835C0132; Sun, 15 Nov 2020 09:07:40 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Sun, 15 Nov 2020 09:07:40 -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:content-type; s=fm2; bh= UXs8CWL0C7rRG7XDmNDrKDhTa3uGvv79P2CT3zZSp5g=; b=REtCxfI9sqzX7MiB t6A2Ob4gL7YjmuMsFt4ZnoAnK21uUe5A21FUOkzNmwMcziuZ1snz+cCvGfCY515W dAL0GIjuOTG4M/Z34lvLByr80FdIEnwa2p845KZh9jM+ZseTsI5YNHiev09pSdmf VuEZdx4Zv4bdCTS2jXgceTtVA7lATBmNkrE/YwoDf/vQaSz/qg6iN4s2qI0+nIar BhkmsvsGbqVon39KEvy5q6KwW211cgUgAgrUv9N54SzRXE3y+NYYF4Oph59mDr1U n1nfwBL7RybU9TVCUzbhTBeZbITb4+cEEVr0ENlGJy7VmTToilt1GHhjzKq6xCkI vLNvNA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :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=UXs8CWL0C7rRG7XDmNDrKDhTa3uGvv79P2CT3zZSp 5g=; b=d9LMSUspouR98jSR4Hj7Fmqwind50PnNl1EquQtKOOKR/fnd1QfpwmX/I St4fdQVDd2lZoRvNpqQAAsvq9+2fc+has8YF0sthgkcok324fzqe5BM1VoDI6OVr OG/TpplJ8XdxxtTUmDyc1MN6+kU/8gXNA2Jjn3LpTJoiKDj3bmXZr8mj9djW/Whk M6FcCPQ/C8+dO9fLwmGpoggkzsODPvDKYcn7wcgvUabReJl2e5iWX/FMJn5PuLuR Mrz2BAo4fI/rIKdst8xNW0StaNSv/E1UGITDaCL5XTvLNRTHVNeCyb63bgeDuWGD GxGtFfGFedl122ZwsDRgvwEsdJiZg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedruddvledgieefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhvffufffkjghfggfgtgesthfure dttddtvdenucfhrhhomhepvfhhohhmrghsucfoohhnjhgrlhhonhcuoehthhhomhgrshes mhhonhhjrghlohhnrdhnvghtqeenucggtffrrghtthgvrhhnpeffvdffjeeuteelfeeile duudeugfetjeelveefkeejfeeigeehteffvdekfeegudenucffohhmrghinhepughpughk rdhorhhgnecukfhppeejjedrudefgedrvddtfedrudekgeenucevlhhushhtvghrufhiii gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghlohhn rdhnvght X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id EDC15328005A; Sun, 15 Nov 2020 09:07:38 -0500 (EST) From: Thomas Monjalon To: orika@mellanox.com, guyk@marvell.com Cc: dev@dpdk.org, jerinj@marvell.com, smadarf@marvell.com, dovrat@marvell.com Date: Sun, 15 Nov 2020 15:07:37 +0100 Message-ID: <2842967.QiQG2SfMXr@thomas> In-Reply-To: <20201018120353.11325-1-guyk@marvell.com> References: <20200908123144.26444-3-guyk@marvell.com> <20201018120353.11325-1-guyk@marvell.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v3 0/2] Add example l3fwd-regex 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" 18/10/2020 14:03, guyk@marvell.com: > From: Guy Kaneti > > The L3 Forwarding with Regex application is a simple example of > packet processing using DPDK Regex framework. > The application performs L3 LPM based forwarding while using > Regex framework for pre-filtering decision. The techboard decision is a bit different of this l3fwd-regex: " - TB agreed to have an example application that exercises the regex device and network device as a separate application. - The example shall be used for both Benchmark and functional verification of regex in the forwarding path. - Based on the discussions, it is agreed that l3fwd might not be the real use case to consider as regex + network application - Instead, TB recommends having the Deep packet inspection style application to showcase the regex + networking use case. - Following is the simple DPI style application definition, which can be considered as a candidate, as an example of regex + network application 1) Create or import a rule database. - Rule database will have an index as rule_id and pattern to search 2) Create or import rule_id to the action table - Action could be -1 for the drop, 0 .. N for a specific port to forward upon the match 3) Enqueue all the packet from ethdev to regexdev 4) If there is a match, then do the action based on the table created in step 2 using struct rte_regexdev_match::rule_id 5) If there is no match, forward back to the source port " http://mails.dpdk.org/archives/dev/2020-November/191301.html