d/numam-dpdk
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

ethdev: add strict queue to pre-configuration flow hints

Browse Source 
The data-path focused flow rule management can manage flow rules in more
optimized way than traditional one by using hints provided by
application in initialization phase.

In addition to the current hints we have in port attr, more hints could
be provided by application about its behaviour.

One example is how the application do with the same flow rule ?
A. create/destroy flow on same queue but query flow on different queue
   or queue-less way (i.e, counter query)
B. All flow operations will be exactly on the same queue, by which PMD
   could be in more optimized way then A because resource could be
   isolated and access based on queue, without lock, for example.

This patch add flag about above situation and could be extended to cover
more situations.

Signed-off-by: Michael Baum <michaelba@nvidia.com>
Acked-by: Ori Kam <orika@nvidia.com>
Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
This commit is contained in:
Michael Baum 2022-10-27 00:49:41 +03:00 committed by Andrew Rybchenko
parent f496b86506
commit dcc9a80c20
3 changed files with 26 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
app/test-pmd/cmdline_flow.c
View File

@ -226,6 +226,7 @@ enum index {
CONFIG_AGING_OBJECTS_NUMBER,
CONFIG_METERS_NUMBER,
CONFIG_CONN_TRACK_NUMBER,
CONFIG_FLAGS,
/* Indirect action arguments */
INDIRECT_ACTION_CREATE,
@ -1092,6 +1093,7 @@ static const enum index next_config_attr[] = {
CONFIG_AGING_OBJECTS_NUMBER,
CONFIG_METERS_NUMBER,
CONFIG_CONN_TRACK_NUMBER,
CONFIG_FLAGS,
END,
ZERO,
};
@ -2692,6 +2694,14 @@ static const struct token token_list[] = {
.args = ARGS(ARGS_ENTRY(struct buffer,
args.configure.port_attr.nb_conn_tracks)),
},
[CONFIG_FLAGS] = {
.name = "flags",
.help = "configuration flags",
.next = NEXT(next_config_attr,
NEXT_ENTRY(COMMON_UNSIGNED)),
.args = ARGS(ARGS_ENTRY(struct buffer,
args.configure.port_attr.flags)),
},
/* Top-level command. */
[PATTERN_TEMPLATE] = {
.name = "pattern_template",

4
doc/guides/testpmd_app_ug/testpmd_funcs.rst
View File

@ -2891,7 +2891,7 @@ following sections.
[queues_number {number}] [queues_size {size}]
[counters_number {number}]
[aging_counters_number {number}]
[meters_number {number}]
[meters_number {number}] [flags {number}]
- Create a pattern template::
flow pattern_template {port_id} create [pattern_template_id {id}]
@ -3042,7 +3042,7 @@ for asynchronous flow creation/destruction operations. It is bound to
[queues_number {number}] [queues_size {size}]
[counters_number {number}]
[aging_counters_number {number}]
[meters_number {number}]
[meters_number {number}] [flags {number}]
If successful, it will show::

14
lib/ethdev/rte_flow.h
View File

@ -4741,6 +4741,12 @@ rte_flow_flex_item_release(uint16_t port_id,
const struct rte_flow_item_flex_handle *handle,
struct rte_flow_error *error);
/**
* Indicate all operations for a given flow rule will _strictly_
* happen on the same queue (create/destroy/query/update).
*/
#define RTE_FLOW_PORT_FLAG_STRICT_QUEUE RTE_BIT32(0)
/**
* @warning
* @b EXPERIMENTAL: this API may change without prior notice.
@ -4774,6 +4780,10 @@ struct rte_flow_port_info {
* @see RTE_FLOW_ACTION_TYPE_CONNTRACK
*/
uint32_t max_nb_conn_tracks;
/**
* Port supported flags (RTE_FLOW_PORT_FLAG_*).
*/
uint32_t supported_flags;
};
/**
@ -4848,6 +4858,10 @@ struct rte_flow_port_attr {
* @see RTE_FLOW_ACTION_TYPE_CONNTRACK
*/
uint32_t nb_conn_tracks;
/**
* Port flags (RTE_FLOW_PORT_FLAG_*).
*/
uint32_t flags;
};
/**