From: Suanming Mou <suanmingm@nvidia.com>
To: Ori Kam <orika@nvidia.com>,
Aman Singh <aman.deep.singh@intel.com>,
"Yuying Zhang" <yuying.zhang@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
"Ferruh Yigit" <ferruh.yigit@xilinx.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Cc: <dev@dpdk.org>
Subject: [PATCH v1] ethdev: add async flow connection tracking configuration
Date: Tue, 20 Sep 2022 10:10:36 +0300 [thread overview]
Message-ID: <20220920071036.20878-1-suanmingm@nvidia.com> (raw)
In-Reply-To: <20220809132534.24441-1-suanmingm@nvidia.com>
In queue based async flow engine, in order to optimize the flow
insertion rate, PMD can use the hints from application to have
resources pre-allocate during initialization phase for actions
such as count/meter/aging.
This commit adds the connection tracking action hints.
Signed-off-by: Suanming Mou <suanmingm@nvidia.com>
Acked-by: Ori Kam <orika@nvidia.com>
---
app/test-pmd/cmdline_flow.c | 10 ++++++++++
doc/guides/rel_notes/release_22_11.rst | 6 ++++++
lib/ethdev/rte_flow.h | 10 ++++++++++
3 files changed, 26 insertions(+)
diff --git a/app/test-pmd/cmdline_flow.c b/app/test-pmd/cmdline_flow.c
index 7f50028eb7..c9cbf381c4 100644
--- a/app/test-pmd/cmdline_flow.c
+++ b/app/test-pmd/cmdline_flow.c
@@ -219,6 +219,7 @@ enum index {
CONFIG_COUNTERS_NUMBER,
CONFIG_AGING_OBJECTS_NUMBER,
CONFIG_METERS_NUMBER,
+ CONFIG_CONN_TRACK_NUMBER,
/* Indirect action arguments */
INDIRECT_ACTION_CREATE,
@@ -1081,6 +1082,7 @@ static const enum index next_config_attr[] = {
CONFIG_COUNTERS_NUMBER,
CONFIG_AGING_OBJECTS_NUMBER,
CONFIG_METERS_NUMBER,
+ CONFIG_CONN_TRACK_NUMBER,
END,
ZERO,
};
@@ -2667,6 +2669,14 @@ static const struct token token_list[] = {
.args = ARGS(ARGS_ENTRY(struct buffer,
args.configure.port_attr.nb_meters)),
},
+ [CONFIG_CONN_TRACK_NUMBER] = {
+ .name = "conn_tracks_number",
+ .help = "number of connection trackings",
+ .next = NEXT(next_config_attr,
+ NEXT_ENTRY(COMMON_UNSIGNED)),
+ .args = ARGS(ARGS_ENTRY(struct buffer,
+ args.configure.port_attr.nb_conn_tracks)),
+ },
/* Top-level command. */
[PATTERN_TEMPLATE] = {
.name = "pattern_template",
diff --git a/doc/guides/rel_notes/release_22_11.rst b/doc/guides/rel_notes/release_22_11.rst
index 8c021cf050..d5e64ff9a1 100644
--- a/doc/guides/rel_notes/release_22_11.rst
+++ b/doc/guides/rel_notes/release_22_11.rst
@@ -55,6 +55,12 @@ New Features
Also, make sure to start the actual text at the margin.
=======================================================
+* **Added configuration for asynchronous flow connection tracking.**
+
+ Added connection tracking action number hint to ``rte_flow_configure``
+ and ``rte_flow_info_get``.
+ PMD can prepare the connection tracking resources according to the hint.
+
Removed Items
-------------
diff --git a/lib/ethdev/rte_flow.h b/lib/ethdev/rte_flow.h
index a79f1e7ef0..c2747abc55 100644
--- a/lib/ethdev/rte_flow.h
+++ b/lib/ethdev/rte_flow.h
@@ -4902,6 +4902,11 @@ struct rte_flow_port_info {
* @see RTE_FLOW_ACTION_TYPE_METER
*/
uint32_t max_nb_meters;
+ /**
+ * Maximum number connection trackings.
+ * @see RTE_FLOW_ACTION_TYPE_CONNTRACK
+ */
+ uint32_t max_nb_conn_tracks;
};
/**
@@ -4971,6 +4976,11 @@ struct rte_flow_port_attr {
* @see RTE_FLOW_ACTION_TYPE_METER
*/
uint32_t nb_meters;
+ /**
+ * Number of connection trackings to configure.
+ * @see RTE_FLOW_ACTION_TYPE_CONNTRACK
+ */
+ uint32_t nb_conn_tracks;
};
/**
--
2.25.1
next prev parent reply other threads:[~2022-09-20 7:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 13:25 [RFC] " Suanming Mou
2022-08-15 12:00 ` Ori Kam
2022-09-13 7:21 ` Suanming Mou
2022-09-13 7:33 ` Ori Kam
2022-09-20 7:10 ` Suanming Mou [this message]
2022-09-28 8:34 ` [PATCH v1] " Andrew Rybchenko
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=20220920071036.20878-1-suanmingm@nvidia.com \
--to=suanmingm@nvidia.com \
--cc=aman.deep.singh@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@xilinx.com \
--cc=orika@nvidia.com \
--cc=thomas@monjalon.net \
--cc=yuying.zhang@intel.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).