DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: orika@mellanox.com, guyk@marvell.com
Cc: dev@dpdk.org, jerinj@marvell.com, smadarf@marvell.com,
Subject: Re: [dpdk-dev] [PATCH v3 0/2] Add example l3fwd-regex
Date: Sun, 15 Nov 2020 15:07:37 +0100	[thread overview]
Message-ID: <2842967.QiQG2SfMXr@thomas> (raw)
In-Reply-To: <20201018120353.11325-1-guyk@marvell.com>

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


  parent reply	other threads:[~2020-11-15 14:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-08 12:31 [dpdk-dev] [PATCH " guyk
2020-09-08 12:31 ` [dpdk-dev] [PATCH 1/2] examples/l3fwd-regex: add regex based l3fwd guyk
2020-10-14  8:47   ` Thomas Monjalon
2020-10-18 11:53     ` [dpdk-dev] [EXT] " Guy Kaneti
2020-10-18 13:32       ` Thomas Monjalon
2020-09-08 12:31 ` [dpdk-dev] [PATCH 2/2] doc: add l3fwd-regex application user guide guyk
2020-09-09 12:08   ` [dpdk-dev] [PATCH v2 0/2] Add example l3fwd-regex guyk
2020-09-09 12:08     ` [dpdk-dev] [PATCH v2 1/2] examples/l3fwd-regex: add regex based l3fwd guyk
2020-10-07 13:44       ` Ori Kam
2020-10-14  8:50       ` Thomas Monjalon
2020-09-09 12:08     ` [dpdk-dev] [PATCH v2 2/2] doc: add l3fwd-regex application user guide guyk
2020-10-07 13:28       ` Ori Kam
2020-10-18 12:03   ` [dpdk-dev] [PATCH v3 0/2] Add example l3fwd-regex guyk
2020-10-18 12:03     ` [dpdk-dev] [PATCH v3 1/2] examples/l3fwd-regex: add regex based l3fwd guyk
2020-10-19 15:09       ` Ori Kam
2020-10-18 12:03     ` [dpdk-dev] [PATCH v3 2/2] doc: add l3fwd-regex application user guide guyk
2020-10-19 15:12       ` Ori Kam
2020-11-15 14:07     ` Thomas Monjalon [this message]
2023-06-29 17:11       ` [dpdk-dev] [PATCH v3 0/2] Add example l3fwd-regex Stephen Hemminger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2842967.QiQG2SfMXr@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=dovrat@marvell.com \
    --cc=guyk@marvell.com \
    --cc=jerinj@marvell.com \
    --cc=orika@mellanox.com \
    --cc=smadarf@marvell.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).