From: Thomas Monjalon <thomas@monjalon.net>
To: Guy Kaneti <guyk@marvell.com>
Cc: "orika@mellanox.com" <orika@mellanox.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Smadar Fuks <smadarf@marvell.com>,
Dovrat Zifroni <dovrat@marvell.com>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
"konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
"honnappa.nagarahalli@arm.com" <honnappa.nagarahalli@arm.com>,
"ktraynor@redhat.com" <ktraynor@redhat.com>
Subject: Re: [dpdk-dev] [EXT] Re: [PATCH 1/2] examples/l3fwd-regex: add regex based l3fwd
Date: Sun, 18 Oct 2020 15:32:47 +0200 [thread overview]
Message-ID: <4674736.E9P3XzJaBd@thomas> (raw)
In-Reply-To: <DM6PR18MB2410F81BAB0D5A6974A5144BD8010@DM6PR18MB2410.namprd18.prod.outlook.com>
18/10/2020 13:53, Guy Kaneti:
> From: Thomas Monjalon <thomas@monjalon.net>
> > > From: Guy Kaneti <guyk@marvell.com>
> > >
> > > Add regex based l3fwd application
> > > inline with normal l3fwd. only LPM is supported.
> >
> > The trend is to reduce the number of example applications.
> > Do you think regex could be an option in the original l3fwd?
>
> The regex operation is not a direct networking functionality and is not a type of forwarding.
> The purpose of the application was to show an example of regex operation with networking.
> I think it should stand by itself.
If it was only regex, yes it would make sense as standalone.
But mixing with networking forwarding could be in the same app.
next prev parent reply other threads:[~2020-10-18 13:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 12:31 [dpdk-dev] [PATCH 0/2] Add example l3fwd-regex 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 [this message]
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 ` [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=4674736.E9P3XzJaBd@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dovrat@marvell.com \
--cc=ferruh.yigit@intel.com \
--cc=guyk@marvell.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=jerinj@marvell.com \
--cc=konstantin.ananyev@intel.com \
--cc=ktraynor@redhat.com \
--cc=orika@mellanox.com \
--cc=smadarf@marvell.com \
/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).