From: Sowmini Varadhan <sovaradh@linux.microsoft.com>
To: sowmini05@gmail.com, bernard.iremonger@intel.com, dev@dpdk.org,
sovaradh@linux.microsoft.com
Cc: thomas@monjalon.net
Subject: [dpdk-dev] [PATCH v2 0/2] TCP flow classification using 4-tuple and flags
Date: Wed, 18 Aug 2021 08:01:12 -0700 [thread overview]
Message-ID: <cover.1629287046.git.sovaradh@linux.microsoft.com> (raw)
V2 updates: checkpatch typo fixes, bernard.iremonger review fixes
The problem space of TCP flow tracking and classification
based on TCP state requires the ability to classify TCP
flows on more packet properties than just the 4-tuple,
e.g., TCP flags. This patch-set provides the set of
changes needed in the examples/flow_classify.c needed to
achieve this.
Patch 1 extends examples/flow_classify.c to allow constraints
on tcp flags. Patch 2 extends the ACL handling in
librte_flow_classify to include keys on the properties in
addition to the tcp 4-tuple.
Sowmini Varadhan (2):
examples/flow_classify: hooks for filters on tcp flags
examples/flow_classify: add an ACL table for tcp
examples/flow_classify/flow_classify.c | 118 +++++++++++++++++---
examples/flow_classify/ipv4_rules_file.txt | 22 ++--
lib/flow_classify/rte_flow_classify.c | 87 +++++++++++++++
lib/flow_classify/rte_flow_classify.h | 19 ++++
lib/flow_classify/rte_flow_classify_parse.c | 8 +-
5 files changed, 228 insertions(+), 26 deletions(-)
--
2.17.1
next reply other threads:[~2021-08-18 15:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 15:01 Sowmini Varadhan [this message]
2021-08-18 15:01 ` [dpdk-dev] [PATCH v2 1/2] examples/flow_classify: hooks for filters on tcp flags Sowmini Varadhan
2021-08-19 16:08 ` Iremonger, Bernard
2021-08-18 15:01 ` [dpdk-dev] [PATCH v2 2/2] examples/flow_classify: add an ACL table for tcp Sowmini Varadhan
2021-08-19 15:06 ` Iremonger, Bernard
2021-08-19 15:20 ` Sowmini Varadhan
2021-08-19 16:21 ` Iremonger, Bernard
2021-08-19 19:34 ` Sowmini Varadhan
2023-07-03 23:38 ` 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=cover.1629287046.git.sovaradh@linux.microsoft.com \
--to=sovaradh@linux.microsoft.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=sowmini05@gmail.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).