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 8C25C42D8E; Thu, 29 Jun 2023 19:11:42 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 7DC62410D0; Thu, 29 Jun 2023 19:11:42 +0200 (CEST) Received: from mail-pj1-f44.google.com (mail-pj1-f44.google.com [209.85.216.44]) by mails.dpdk.org (Postfix) with ESMTP id F0D5E406B7 for <dev@dpdk.org>; Thu, 29 Jun 2023 19:11:40 +0200 (CEST) Received: by mail-pj1-f44.google.com with SMTP id 98e67ed59e1d1-262e81f6154so537256a91.2 for <dev@dpdk.org>; Thu, 29 Jun 2023 10:11:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20221208.gappssmtp.com; s=20221208; t=1688058700; x=1690650700; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=3Za6hEO2KuAW/4ezc+dW8DWa71ftLCAixdAsx9rIQas=; b=CNdZPA8ji0szQTq7FmNwfYK0X9ByKGIJvCBXnFOfEGNEEKX+57qnNoCAbBbHAKaS0F jbeVtBAYGzKiO7HurIRLgAO7t4e1MIQFNEyiuwRuVEyxeZrJmNVDQJxPcDWfQPaH9gXc enDE/Z2jHUnDZaqr0eywkrMDfR8XVka7fZ6A7KWmF+d9yBUU6/coXS7ZDCqDEgNHzHcC HWKTwtw9yWLlDSJ/GuLw+6DSDf6vZokLkr0bLIfACgThX2a5W/4OS6uXtlI74xm4k0cg gKgQ1iW81YcyQuDr0ZOEQf1wyUHwri/kVNSzVVQaSrKMR0mGrtqdVyr/TzR6KZsozbIB wVuQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1688058700; x=1690650700; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=3Za6hEO2KuAW/4ezc+dW8DWa71ftLCAixdAsx9rIQas=; b=EZbDpWOq7zdv3/wdrdXBhAqKGCxVtdvm3dpK7ce10pi+1Ht8vKk7LdtVq7gnJ+kMOb BgMbaPQJ863PVrBYyi+NTNTUsJu1+xn1RG/KcxEsEP5+9RnIRzXQ7bJDW5EqUQvB4+vA Tf1gMnyoMCP0CCs92p+YPIkTz3YZIScAVgrv6TAPgzhhCyARYUlI8FJRL3ZHTTYWs3Kp PX3iSteA6gawwlldtKlRHznTAiW++HCCwwprFs988BOGFA73kl52fW+QM9m8lTcG+DxX 9yf07xyFsmvuMFkuljsbjtY5adHaVualFWLTUqh+KhJsfAeczjpbT+tMgMw5b8YvWUgr nmSA== X-Gm-Message-State: ABy/qLYOg0wixjMRGZ55NP0RFK7YCGBgiANk9rCk0iJzI6nOCXeta8rg Q1OxlO7CuTPyDHvj6p7QxQ53bQ== X-Google-Smtp-Source: APBJJlFM7NaA9mEE4gLhgcqyNaVOuctYMSL7BkWV8ryWdSEaehDNyp5SfmYCNoDGyxwufA3wpiuNJQ== X-Received: by 2002:a17:90a:4e82:b0:25e:d727:6fb4 with SMTP id o2-20020a17090a4e8200b0025ed7276fb4mr113862pjh.2.1688058700170; Thu, 29 Jun 2023 10:11:40 -0700 (PDT) Received: from hermes.local (204-195-120-218.wavecable.com. [204.195.120.218]) by smtp.gmail.com with ESMTPSA id pj1-20020a17090b4f4100b00256bbfbabcfsm11142432pjb.48.2023.06.29.10.11.39 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 29 Jun 2023 10:11:39 -0700 (PDT) Date: Thu, 29 Jun 2023 10:11:38 -0700 From: Stephen Hemminger <stephen@networkplumber.org> To: Thomas Monjalon <thomas@monjalon.net> Cc: orika@mellanox.com, guyk@marvell.com, dev@dpdk.org, jerinj@marvell.com, smadarf@marvell.com, dovrat@marvell.com Subject: Re: [dpdk-dev] [PATCH v3 0/2] Add example l3fwd-regex Message-ID: <20230629101138.28541118@hermes.local> In-Reply-To: <2842967.QiQG2SfMXr@thomas> References: <20200908123144.26444-3-guyk@marvell.com> <20201018120353.11325-1-guyk@marvell.com> <2842967.QiQG2SfMXr@thomas> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 On Sun, 15 Nov 2020 15:07:37 +0100 Thomas Monjalon <thomas@monjalon.net> wrote: > 18/10/2020 14:03, guyk@marvell.com: > > From: Guy Kaneti <guyk@marvell.com> > > > > 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 Marking original example as "Changes requested" Please resubmit example based on the above feedback.