From: <guyk@marvell.com>
To: <thomas@monjalon.net>, <orika@mellanox.com>,
<john.mcnamara@intel.com>, <marko.kovacevic@intel.com>
Cc: <dev@dpdk.org>, <guyk@marvell.com>, <jerinj@marvell.com>,
<smadarf@marvell.com>, <dovrat@marvell.com>
Subject: [dpdk-dev] [PATCH v3 0/2] Add example l3fwd-regex
Date: Sun, 18 Oct 2020 15:03:51 +0300 [thread overview]
Message-ID: <20201018120353.11325-1-guyk@marvell.com> (raw)
In-Reply-To: <20200908123144.26444-3-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.
v3:
* Rebase.
* fix typo
v2:
* Rebase.
* Add release notes.
* fix spelling mistake
* fix build error
Guy Kaneti (2):
examples/l3fwd-regex: add regex based l3fwd
doc: add l3fwd-regex application user guide
MAINTAINERS | 3 +
doc/guides/rel_notes/release_20_11.rst | 5 +
doc/guides/sample_app_ug/index.rst | 1 +
doc/guides/sample_app_ug/intro.rst | 4 +
doc/guides/sample_app_ug/l3_forward_regex.rst | 235 ++++
examples/l3fwd-regex/l3fwd.h | 207 +++
examples/l3fwd-regex/l3fwd_lpm.c | 484 +++++++
examples/l3fwd-regex/l3fwd_regex.c | 487 +++++++
examples/l3fwd-regex/l3fwd_regex.h | 38 +
examples/l3fwd-regex/main.c | 1117 +++++++++++++++++
examples/l3fwd-regex/meson.build | 10 +
examples/meson.build | 2 +-
12 files changed, 2592 insertions(+), 1 deletion(-)
create mode 100644 doc/guides/sample_app_ug/l3_forward_regex.rst
create mode 100644 examples/l3fwd-regex/l3fwd.h
create mode 100644 examples/l3fwd-regex/l3fwd_lpm.c
create mode 100644 examples/l3fwd-regex/l3fwd_regex.c
create mode 100644 examples/l3fwd-regex/l3fwd_regex.h
create mode 100644 examples/l3fwd-regex/main.c
create mode 100644 examples/l3fwd-regex/meson.build
--
2.28.0
next prev parent reply other threads:[~2020-10-18 12:05 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 ` guyk [this message]
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 ` [dpdk-dev] [PATCH v3 0/2] Add example l3fwd-regex Thomas Monjalon
2023-06-29 17:11 ` 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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201018120353.11325-1-guyk@marvell.com \
--to=guyk@marvell.com \
--cc=dev@dpdk.org \
--cc=dovrat@marvell.com \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=orika@mellanox.com \
--cc=smadarf@marvell.com \
--cc=thomas@monjalon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).