From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: Ori Kam <orika@nvidia.com>,
Alexander Kozyrev <akozyrev@nvidia.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
"ivan.malov@oktetlabs.ru" <ivan.malov@oktetlabs.ru>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
"mohammad.abdul.awal@intel.com" <mohammad.abdul.awal@intel.com>,
"qi.z.zhang@intel.com" <qi.z.zhang@intel.com>,
"jerinj@marvell.com" <jerinj@marvell.com>,
"ajit.khaparde@broadcom.com" <ajit.khaparde@broadcom.com>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>
Subject: Re: [PATCH v8 02/11] ethdev: add flow item/action templates
Date: Mon, 21 Feb 2022 18:05:43 +0300 [thread overview]
Message-ID: <5d8e0b32-f674-a43f-20ee-a689ab7c2012@oktetlabs.ru> (raw)
In-Reply-To: <MW2PR12MB46662932E8CAE20782F826B5D63A9@MW2PR12MB4666.namprd12.prod.outlook.com>
On 2/21/22 16:12, Ori Kam wrote:
> Hi Andrew,
>
>> -----Original Message-----
>> From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
>> Sent: Monday, February 21, 2022 12:57 PM
>> Subject: Re: [PATCH v8 02/11] ethdev: add flow item/action templates
>>
>> On 2/20/22 06:44, Alexander Kozyrev wrote:
>>> Treating every single flow rule as a completely independent and separate
>>> entity negatively impacts the flow rules insertion rate. Oftentimes in an
>>> application, many flow rules share a common structure (the same item mask
>>> and/or action list) so they can be grouped and classified together.
>>> This knowledge may be used as a source of optimization by a PMD/HW.
>>>
>>> The pattern template defines common matching fields (the item mask) without
>>> values. The actions template holds a list of action types that will be used
>>> together in the same rule. The specific values for items and actions will
>>> be given only during the rule creation.
>>>
>>> A table combines pattern and actions templates along with shared flow rule
>>> attributes (group ID, priority and traffic direction). This way a PMD/HW
>>> can prepare all the resources needed for efficient flow rules creation in
>>> the datapath. To avoid any hiccups due to memory reallocation, the maximum
>>> number of flow rules is defined at the table creation time.
>>>
>>> The flow rule creation is done by selecting a table, a pattern template
>>> and an actions template (which are bound to the table), and setting unique
>>> values for the items and actions.
>>>
>>> Signed-off-by: Alexander Kozyrev <akozyrev@nvidia.com>
>>> Acked-by: Ori Kam <orika@nvidia.com>
>>
>> [snip]
>>
>>> +For example, to create an actions template with the same Mark ID
>>> +but different Queue Index for every rule:
>>> +
>>> +.. code-block:: c
>>> +
>>> + rte_flow_actions_template_attr attr = {.ingress = 1};
>>> + struct rte_flow_action act[] = {
>>> + /* Mark ID is 4 for every rule, Queue Index is unique */
>>> + [0] = {.type = RTE_FLOW_ACTION_TYPE_MARK,
>>> + .conf = &(struct rte_flow_action_mark){.id = 4}},
>>> + [1] = {.type = RTE_FLOW_ACTION_TYPE_QUEUE},
>>> + [2] = {.type = RTE_FLOW_ACTION_TYPE_END,},
>>> + };
>>> + struct rte_flow_action msk[] = {
>>> + /* Assign to MARK mask any non-zero value to make it constant */
>>> + [0] = {.type = RTE_FLOW_ACTION_TYPE_MARK,
>>> + .conf = &(struct rte_flow_action_mark){.id = 1}},
>>
>> 1 looks very strange. I can understand it in the case of
>> integer and boolean fields, but what to do in the case of
>> arrays? IMHO, it would be better to use all 0xff's in value.
>> Anyway, it must be defined very carefully and non-ambiguous.
>>
> There is some issues with all 0xff for example in case of pointers or
> enums this it will result in invalid value.
> So I vote for saving it as is.
> I fully agree that it should be defined very clearly.
> I think that for arrays with predefined size (I don't think we have such in rte_flow)
> it should be declared that that the first element should not be 0.
It is good that we agree that the aspect should be documented
very carefully. Let's do it.
>
>>> + [1] = {.type = RTE_FLOW_ACTION_TYPE_QUEUE},
>>> + [2] = {.type = RTE_FLOW_ACTION_TYPE_END,},
>>> + };
>>> + struct rte_flow_error err;
>>> +
>>> + struct rte_flow_actions_template *actions_template =
>>> + rte_flow_actions_template_create(port, &attr, &act, &msk, &err);
>>> +
>>> +The concrete value for Queue Index will be provided at the rule creation.
>>
>> [snip]
>>
>>> diff --git a/lib/ethdev/rte_flow.c b/lib/ethdev/rte_flow.c
>>> index ffd48e40d5..e9f684eedb 100644
>>> --- a/lib/ethdev/rte_flow.c
>>> +++ b/lib/ethdev/rte_flow.c
>>> @@ -1461,3 +1461,255 @@ rte_flow_configure(uint16_t port_id,
>>> RTE_FLOW_ERROR_TYPE_UNSPECIFIED,
>>> NULL, rte_strerror(ENOTSUP));
>>> }
>>> +
>>> +struct rte_flow_pattern_template *
>>> +rte_flow_pattern_template_create(uint16_t port_id,
>>> + const struct rte_flow_pattern_template_attr *template_attr,
>>> + const struct rte_flow_item pattern[],
>>> + struct rte_flow_error *error)
>>> +{
>>> + struct rte_eth_dev *dev = &rte_eth_devices[port_id];
>>> + const struct rte_flow_ops *ops = rte_flow_ops_get(port_id, error);
>>> + struct rte_flow_pattern_template *template;
>>> +
>>> + if (template_attr == NULL) {
>>> + RTE_FLOW_LOG(ERR,
>>> + "Port %"PRIu16" template attr is NULL.\n",
>>> + port_id);
>>> + rte_flow_error_set(error, EINVAL,
>>> + RTE_FLOW_ERROR_TYPE_ATTR,
>>> + NULL, rte_strerror(EINVAL));
>>> + return NULL;
>>> + }
>>> + if (pattern == NULL) {
>>> + RTE_FLOW_LOG(ERR,
>>> + "Port %"PRIu16" pattern is NULL.\n",
>>> + port_id);
>>> + rte_flow_error_set(error, EINVAL,
>>> + RTE_FLOW_ERROR_TYPE_ATTR,
>>> + NULL, rte_strerror(EINVAL));
>>> + return NULL;
>>> + }
>>> + if (dev->data->flow_configured == 0) {
>>> + RTE_FLOW_LOG(INFO,
>>> + "Flow engine on port_id=%"PRIu16" is not configured.\n",
>>> + port_id);
>>> + rte_flow_error_set(error, EINVAL,
>>> + RTE_FLOW_ERROR_TYPE_STATE,
>>> + NULL, rte_strerror(EINVAL));
>>> + return NULL;
>>> + }
>>> + if (unlikely(!ops))
>>> + return NULL;
>>
>> See notes about order of checks in previous patch review notes.
>>
>>> + if (likely(!!ops->pattern_template_create)) {
>>> + template = ops->pattern_template_create(dev, template_attr,
>>> + pattern, error);
>>> + if (template == NULL)
>>> + flow_err(port_id, -rte_errno, error);
>>> + return template;
>>> + }
>>> + rte_flow_error_set(error, ENOTSUP,
>>> + RTE_FLOW_ERROR_TYPE_UNSPECIFIED,
>>> + NULL, rte_strerror(ENOTSUP));
>>> + return NULL;
>>> +}
>>> +
>>> +int
>>> +rte_flow_pattern_template_destroy(uint16_t port_id,
>>> + struct rte_flow_pattern_template *pattern_template,
>>> + struct rte_flow_error *error)
>>> +{
>>> + struct rte_eth_dev *dev = &rte_eth_devices[port_id];
>>> + const struct rte_flow_ops *ops = rte_flow_ops_get(port_id, error);
>>> +
>>> + if (unlikely(pattern_template == NULL))
>>> + return 0;
>>> + if (unlikely(!ops))
>>> + return -rte_errno;
>>
>> Same here. I'm afraid it is really important here as well,
>> since request should not return OK if port_id is invalid.
>>
>>
>>> + if (likely(!!ops->pattern_template_destroy)) {
>>> + return flow_err(port_id,
>>> + ops->pattern_template_destroy(dev,
>>> + pattern_template,
>>> + error),
>>> + error);
>>> + }
>>> + return rte_flow_error_set(error, ENOTSUP,
>>> + RTE_FLOW_ERROR_TYPE_UNSPECIFIED,
>>> + NULL, rte_strerror(ENOTSUP));
>>> +}
>>> +
>>> +struct rte_flow_actions_template *
>>> +rte_flow_actions_template_create(uint16_t port_id,
>>> + const struct rte_flow_actions_template_attr *template_attr,
>>> + const struct rte_flow_action actions[],
>>> + const struct rte_flow_action masks[],
>>> + struct rte_flow_error *error)
>>> +{
>>> + struct rte_eth_dev *dev = &rte_eth_devices[port_id];
>>> + const struct rte_flow_ops *ops = rte_flow_ops_get(port_id, error);
>>> + struct rte_flow_actions_template *template;
>>> +
>>> + if (template_attr == NULL) {
>>> + RTE_FLOW_LOG(ERR,
>>> + "Port %"PRIu16" template attr is NULL.\n",
>>> + port_id);
>>> + rte_flow_error_set(error, EINVAL,
>>> + RTE_FLOW_ERROR_TYPE_ATTR,
>>> + NULL, rte_strerror(EINVAL));
>>> + return NULL;
>>> + }
>>> + if (actions == NULL) {
>>> + RTE_FLOW_LOG(ERR,
>>> + "Port %"PRIu16" actions is NULL.\n",
>>> + port_id);
>>> + rte_flow_error_set(error, EINVAL,
>>> + RTE_FLOW_ERROR_TYPE_ATTR,
>>> + NULL, rte_strerror(EINVAL));
>>> + return NULL;
>>> + }
>>> + if (masks == NULL) {
>>> + RTE_FLOW_LOG(ERR,
>>> + "Port %"PRIu16" masks is NULL.\n",
>>> + port_id);
>>> + rte_flow_error_set(error, EINVAL,
>>> + RTE_FLOW_ERROR_TYPE_ATTR,
>>> + NULL, rte_strerror(EINVAL));
>>> +
>>> + }
>>> + if (dev->data->flow_configured == 0) {
>>> + RTE_FLOW_LOG(INFO,
>>> + "Flow engine on port_id=%"PRIu16" is not configured.\n",
>>> + port_id);
>>> + rte_flow_error_set(error, EINVAL,
>>> + RTE_FLOW_ERROR_TYPE_STATE,
>>> + NULL, rte_strerror(EINVAL));
>>> + return NULL;
>>> + }
>>> + if (unlikely(!ops))
>>> + return NULL;
>>
>> same here
>>
>>> + if (likely(!!ops->actions_template_create)) {
>>> + template = ops->actions_template_create(dev, template_attr,
>>> + actions, masks, error);
>>> + if (template == NULL)
>>> + flow_err(port_id, -rte_errno, error);
>>> + return template;
>>> + }
>>> + rte_flow_error_set(error, ENOTSUP,
>>> + RTE_FLOW_ERROR_TYPE_UNSPECIFIED,
>>> + NULL, rte_strerror(ENOTSUP));
>>> + return NULL;
>>> +}
>>> +
>>> +int
>>> +rte_flow_actions_template_destroy(uint16_t port_id,
>>> + struct rte_flow_actions_template *actions_template,
>>> + struct rte_flow_error *error)
>>> +{
>>> + struct rte_eth_dev *dev = &rte_eth_devices[port_id];
>>> + const struct rte_flow_ops *ops = rte_flow_ops_get(port_id, error);
>>> +
>>> + if (unlikely(actions_template == NULL))
>>> + return 0;
>>> + if (unlikely(!ops))
>>> + return -rte_errno;
>>
>> same here
>>
>>> + if (likely(!!ops->actions_template_destroy)) {
>>> + return flow_err(port_id,
>>> + ops->actions_template_destroy(dev,
>>> + actions_template,
>>> + error),
>>> + error);
>>> + }
>>> + return rte_flow_error_set(error, ENOTSUP,
>>> + RTE_FLOW_ERROR_TYPE_UNSPECIFIED,
>>> + NULL, rte_strerror(ENOTSUP));
>>> +}
>>> +
>>> +struct rte_flow_template_table *
>>> +rte_flow_template_table_create(uint16_t port_id,
>>> + const struct rte_flow_template_table_attr *table_attr,
>>> + struct rte_flow_pattern_template *pattern_templates[],
>>> + uint8_t nb_pattern_templates,
>>> + struct rte_flow_actions_template *actions_templates[],
>>> + uint8_t nb_actions_templates,
>>> + struct rte_flow_error *error)
>>> +{
>>> + struct rte_eth_dev *dev = &rte_eth_devices[port_id];
>>> + const struct rte_flow_ops *ops = rte_flow_ops_get(port_id, error);
>>> + struct rte_flow_template_table *table;
>>> +
>>> + if (table_attr == NULL) {
>>> + RTE_FLOW_LOG(ERR,
>>> + "Port %"PRIu16" table attr is NULL.\n",
>>> + port_id);
>>> + rte_flow_error_set(error, EINVAL,
>>> + RTE_FLOW_ERROR_TYPE_ATTR,
>>> + NULL, rte_strerror(EINVAL));
>>> + return NULL;
>>> + }
>>> + if (pattern_templates == NULL) {
>>> + RTE_FLOW_LOG(ERR,
>>> + "Port %"PRIu16" pattern templates is NULL.\n",
>>> + port_id);
>>> + rte_flow_error_set(error, EINVAL,
>>> + RTE_FLOW_ERROR_TYPE_ATTR,
>>> + NULL, rte_strerror(EINVAL));
>>> + return NULL;
>>> + }
>>> + if (actions_templates == NULL) {
>>> + RTE_FLOW_LOG(ERR,
>>> + "Port %"PRIu16" actions templates is NULL.\n",
>>> + port_id);
>>> + rte_flow_error_set(error, EINVAL,
>>> + RTE_FLOW_ERROR_TYPE_ATTR,
>>> + NULL, rte_strerror(EINVAL));
>>> + return NULL;
>>> + }
>>> + if (dev->data->flow_configured == 0) {
>>> + RTE_FLOW_LOG(INFO,
>>> + "Flow engine on port_id=%"PRIu16" is not configured.\n",
>>> + port_id);
>>> + rte_flow_error_set(error, EINVAL,
>>> + RTE_FLOW_ERROR_TYPE_STATE,
>>> + NULL, rte_strerror(EINVAL));
>>> + return NULL;
>>> + }
>>> + if (unlikely(!ops))
>>> + return NULL;
>>
>> Order of checks
>>
>>> + if (likely(!!ops->template_table_create)) {
>>> + table = ops->template_table_create(dev, table_attr,
>>> + pattern_templates, nb_pattern_templates,
>>> + actions_templates, nb_actions_templates,
>>> + error);
>>> + if (table == NULL)
>>> + flow_err(port_id, -rte_errno, error);
>>> + return table;
>>> + }
>>> + rte_flow_error_set(error, ENOTSUP,
>>> + RTE_FLOW_ERROR_TYPE_UNSPECIFIED,
>>> + NULL, rte_strerror(ENOTSUP));
>>> + return NULL;
>>> +}
>>> +
>>> +int
>>> +rte_flow_template_table_destroy(uint16_t port_id,
>>> + struct rte_flow_template_table *template_table,
>>> + struct rte_flow_error *error)
>>> +{
>>> + struct rte_eth_dev *dev = &rte_eth_devices[port_id];
>>> + const struct rte_flow_ops *ops = rte_flow_ops_get(port_id, error);
>>> +
>>> + if (unlikely(template_table == NULL))
>>> + return 0;
>>> + if (unlikely(!ops))
>>> + return -rte_errno;
>>> + if (likely(!!ops->template_table_destroy)) {
>>> + return flow_err(port_id,
>>> + ops->template_table_destroy(dev,
>>> + template_table,
>>> + error),
>>> + error);
>>> + }
>>> + return rte_flow_error_set(error, ENOTSUP,
>>> + RTE_FLOW_ERROR_TYPE_UNSPECIFIED,
>>> + NULL, rte_strerror(ENOTSUP));
>>> +}
>>> diff --git a/lib/ethdev/rte_flow.h b/lib/ethdev/rte_flow.h
>>> index cdb7b2be68..776e8ccc11 100644
>>> --- a/lib/ethdev/rte_flow.h
>>> +++ b/lib/ethdev/rte_flow.h
>>> @@ -4983,6 +4983,280 @@ rte_flow_configure(uint16_t port_id,
>>> const struct rte_flow_port_attr *port_attr,
>>> struct rte_flow_error *error);
>>>
>>> +/**
>>> + * Opaque type returned after successful creation of pattern template.
>>> + * This handle can be used to manage the created pattern template.
>>> + */
>>> +struct rte_flow_pattern_template;
>>> +
>>> +/**
>>> + * @warning
>>> + * @b EXPERIMENTAL: this API may change without prior notice.
>>> + *
>>> + * Flow pattern template attributes.
>>
>> Would it be useful to mentioned that at least one direction
>> bit must be set? Otherwise request does not make sense.
>>
> Agree one direction must be set.
>
>>> + */
>>> +__extension__
>>> +struct rte_flow_pattern_template_attr {
>>> + /**
>>> + * Relaxed matching policy.
>>> + * - PMD may match only on items with mask member set and skip
>>> + * matching on protocol layers specified without any masks.
>>> + * - If not set, PMD will match on protocol layers
>>> + * specified without any masks as well.
>>> + * - Packet data must be stacked in the same order as the
>>> + * protocol layers to match inside packets, starting from the lowest.
>>> + */
>>> + uint32_t relaxed_matching:1;
>>
>> I should notice this earlier, but it looks like a new feature
>> which sounds unrelated to templates. If so, it makes asymmetry
>> in sync and async flow rules capabilities.
>> Am I missing something?
>>
>> Anyway, the feature looks hidden in the patch.
>>
> No this is not hidden feature.
> In current API application must specify all the preciding items,
> For example application wants to match on udp source port.
> The rte flow will look something like eth / ipv4/ udp sport = xxx ..
> When PMD gets this pattern it must enforce the after the eth
> there will be IPv4 and then UDP and then add the match for the
> sport.
> This means that the PMD addes extra matching.
> If the application already validated that there is udp in the packet
> in group 0 and then jump to group 1 it can save the HW those extra matching
> by enabling this bit which means that the HW should only match on implicit
> masked fields.
Old API allows to insert rule to non-0 table as well.
So, similar logic could be applicable. Do we want to
have the same feature in old API?
>
>>> + /** Pattern valid for rules applied to ingress traffic. */
>>> + uint32_t ingress:1;
>>> + /** Pattern valid for rules applied to egress traffic. */
>>> + uint32_t egress:1;
>>> + /** Pattern valid for rules applied to transfer traffic. */
>>> + uint32_t transfer:1;
>>> +};
>>> +
>>> +/**
>>> + * @warning
>>> + * @b EXPERIMENTAL: this API may change without prior notice.
>>> + *
>>> + * Create flow pattern template.
>>> + *
>>> + * The pattern template defines common matching fields without values.
>>> + * For example, matching on 5 tuple TCP flow, the template will be
>>> + * eth(null) + IPv4(source + dest) + TCP(s_port + d_port),
>>> + * while values for each rule will be set during the flow rule creation.
>>> + * The number and order of items in the template must be the same
>>> + * at the rule creation.
>>> + *
>>> + * @param port_id
>>> + * Port identifier of Ethernet device.
>>> + * @param[in] template_attr
>>> + * Pattern template attributes.
>>> + * @param[in] pattern
>>> + * Pattern specification (list terminated by the END pattern item).
>>> + * The spec member of an item is not used unless the end member is used.
>>> + * @param[out] error
>>> + * Perform verbose error reporting if not NULL.
>>> + * PMDs initialize this structure in case of error only.
>>> + *
>>> + * @return
>>> + * Handle on success, NULL otherwise and rte_errno is set.
>>
>> Don't we want to be explicit about used negative error code?
>> The question is applicable to all functions.
>>
> Same answer as given in other patch.
> Since PMD may have different/extra error codes I don't think we should
> give them here.
>
>> [snip]
>>
>>> +/**
>>> + * @warning
>>> + * @b EXPERIMENTAL: this API may change without prior notice.
>>> + *
>>> + * Flow actions template attributes.
>>
>> Same question about no directions specified.
>>
>>> + */
>>> +__extension__
>>> +struct rte_flow_actions_template_attr {
>>> + /** Action valid for rules applied to ingress traffic. */
>>> + uint32_t ingress:1;
>>> + /** Action valid for rules applied to egress traffic. */
>>> + uint32_t egress:1;
>>> + /** Action valid for rules applied to transfer traffic. */
>>> + uint32_t transfer:1;
>>> +};
>>> +
>>> +/**
>>> + * @warning
>>> + * @b EXPERIMENTAL: this API may change without prior notice.
>>> + *
>>> + * Create flow actions template.
>>> + *
>>> + * The actions template holds a list of action types without values.
>>> + * For example, the template to change TCP ports is TCP(s_port + d_port),
>>> + * while values for each rule will be set during the flow rule creation.
>>> + * The number and order of actions in the template must be the same
>>> + * at the rule creation.
>>> + *
>>> + * @param port_id
>>> + * Port identifier of Ethernet device.
>>> + * @param[in] template_attr
>>> + * Template attributes.
>>> + * @param[in] actions
>>> + * Associated actions (list terminated by the END action).
>>> + * The spec member is only used if @p masks spec is non-zero.
>>> + * @param[in] masks
>>> + * List of actions that marks which of the action's member is constant.
>>> + * A mask has the same format as the corresponding action.
>>> + * If the action field in @p masks is not 0,
>>
>> Comparison with zero makes sense for integers only.
>>
>
> Why? It can also be with pointers enums.
It should be NULL for pointers and enum-specific member of
enum.
>
>>> + * the corresponding value in an action from @p actions will be the part
>>> + * of the template and used in all flow rules.
>>> + * The order of actions in @p masks is the same as in @p actions.
>>> + * In case of indirect actions present in @p actions,
>>> + * the actual action type should be present in @p mask.
>>> + * @param[out] error
>>> + * Perform verbose error reporting if not NULL.
>>> + * PMDs initialize this structure in case of error only.
>>> + *
>>> + * @return
>>> + * Handle on success, NULL otherwise and rte_errno is set.
>>> + */
>>> +__rte_experimental
>>> +struct rte_flow_actions_template *
>>> +rte_flow_actions_template_create(uint16_t port_id,
>>> + const struct rte_flow_actions_template_attr *template_attr,
>>> + const struct rte_flow_action actions[],
>>> + const struct rte_flow_action masks[],
>>> + struct rte_flow_error *error);
>>
>> [snip]
>
> Best,
> Ori
>
next prev parent reply other threads:[~2022-02-21 15:05 UTC|newest]
Thread overview: 218+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220206032526.816079-1-akozyrev@nvidia.com >
2022-02-09 21:37 ` [PATCH v4 00/10] ethdev: datapath-focused flow rules management Alexander Kozyrev
2022-02-09 21:38 ` [PATCH v4 01/10] ethdev: introduce flow pre-configuration hints Alexander Kozyrev
2022-02-09 21:38 ` [PATCH v4 02/10] ethdev: add flow item/action templates Alexander Kozyrev
2022-02-09 21:38 ` [PATCH v4 03/10] ethdev: bring in async queue-based flow rules operations Alexander Kozyrev
2022-02-09 21:38 ` [PATCH v4 04/10] app/testpmd: implement rte flow configuration Alexander Kozyrev
2022-02-10 9:32 ` Thomas Monjalon
2022-02-09 21:38 ` [PATCH v4 05/10] app/testpmd: implement rte flow template management Alexander Kozyrev
2022-02-09 21:38 ` [PATCH v4 06/10] app/testpmd: implement rte flow table management Alexander Kozyrev
2022-02-09 21:38 ` [PATCH v4 07/10] app/testpmd: implement rte flow queue flow operations Alexander Kozyrev
2022-02-09 21:53 ` Ori Kam
2022-02-09 21:38 ` [PATCH v4 08/10] app/testpmd: implement rte flow push operations Alexander Kozyrev
2022-02-09 21:38 ` [PATCH v4 09/10] app/testpmd: implement rte flow pull operations Alexander Kozyrev
2022-02-09 21:38 ` [PATCH v4 10/10] app/testpmd: implement rte flow queue indirect actions Alexander Kozyrev
2022-02-10 16:00 ` [PATCH v4 00/10] ethdev: datapath-focused flow rules management Ferruh Yigit
2022-02-10 16:12 ` Asaf Penso
2022-02-10 16:33 ` Suanming Mou
2022-02-10 18:04 ` Ajit Khaparde
2022-02-11 10:22 ` Ivan Malov
2022-02-11 10:48 ` Jerin Jacob
2022-02-11 2:26 ` [PATCH v5 " Alexander Kozyrev
2022-02-11 2:26 ` [PATCH v5 01/10] ethdev: introduce flow pre-configuration hints Alexander Kozyrev
2022-02-11 10:16 ` Andrew Rybchenko
2022-02-11 18:47 ` Alexander Kozyrev
2022-02-16 13:03 ` Andrew Rybchenko
2022-02-16 22:17 ` Alexander Kozyrev
2022-02-17 10:35 ` Andrew Rybchenko
2022-02-17 10:57 ` Ori Kam
2022-02-17 11:04 ` Andrew Rybchenko
2022-02-11 2:26 ` [PATCH v5 02/10] ethdev: add flow item/action templates Alexander Kozyrev
2022-02-11 11:27 ` Andrew Rybchenko
2022-02-11 22:25 ` Alexander Kozyrev
2022-02-16 13:14 ` Andrew Rybchenko
2022-02-16 14:18 ` Ori Kam
2022-02-17 10:44 ` Andrew Rybchenko
2022-02-17 11:11 ` Ori Kam
2022-02-11 2:26 ` [PATCH v5 03/10] ethdev: bring in async queue-based flow rules operations Alexander Kozyrev
2022-02-11 12:42 ` Andrew Rybchenko
2022-02-12 2:19 ` Alexander Kozyrev
2022-02-12 9:25 ` Thomas Monjalon
2022-02-16 22:49 ` Alexander Kozyrev
2022-02-17 8:18 ` Thomas Monjalon
2022-02-17 11:02 ` Andrew Rybchenko
2022-02-16 13:34 ` Andrew Rybchenko
2022-02-16 14:53 ` Ori Kam
2022-02-17 10:52 ` Andrew Rybchenko
2022-02-17 11:08 ` Ori Kam
2022-02-17 14:16 ` Ori Kam
2022-02-17 14:34 ` Thomas Monjalon
2022-02-16 15:15 ` Ori Kam
2022-02-17 11:10 ` Andrew Rybchenko
2022-02-17 11:19 ` Ori Kam
2022-02-11 2:26 ` [PATCH v5 04/10] app/testpmd: add flow engine configuration Alexander Kozyrev
2022-02-11 2:26 ` [PATCH v5 05/10] app/testpmd: add flow template management Alexander Kozyrev
2022-02-11 2:26 ` [PATCH v5 06/10] app/testpmd: add flow table management Alexander Kozyrev
2022-02-11 2:26 ` [PATCH v5 07/10] app/testpmd: add async flow create/destroy operations Alexander Kozyrev
2022-02-11 2:26 ` [PATCH v5 08/10] app/testpmd: add flow queue push operation Alexander Kozyrev
2022-02-11 2:26 ` [PATCH v5 09/10] app/testpmd: add flow queue pull operation Alexander Kozyrev
2022-02-11 2:26 ` [PATCH v5 10/10] app/testpmd: add async indirect actions creation/destruction Alexander Kozyrev
2022-02-12 4:19 ` [PATCH v6 00/10] ethdev: datapath-focused flow rules management Alexander Kozyrev
2022-02-12 4:19 ` [PATCH v6 01/10] ethdev: introduce flow pre-configuration hints Alexander Kozyrev
2022-02-12 4:19 ` [PATCH v6 02/10] ethdev: add flow item/action templates Alexander Kozyrev
2022-02-12 4:19 ` [PATCH v6 03/10] ethdev: bring in async queue-based flow rules operations Alexander Kozyrev
2022-02-12 4:19 ` [PATCH v6 04/10] app/testpmd: add flow engine configuration Alexander Kozyrev
2022-02-12 4:19 ` [PATCH v6 05/10] app/testpmd: add flow template management Alexander Kozyrev
2022-02-12 4:19 ` [PATCH v6 06/10] app/testpmd: add flow table management Alexander Kozyrev
2022-02-12 4:19 ` [PATCH v6 07/10] app/testpmd: add async flow create/destroy operations Alexander Kozyrev
2022-02-12 4:19 ` [PATCH v6 08/10] app/testpmd: add flow queue push operation Alexander Kozyrev
2022-02-12 4:19 ` [PATCH v6 09/10] app/testpmd: add flow queue pull operation Alexander Kozyrev
2022-02-12 4:19 ` [PATCH v6 10/10] app/testpmd: add async indirect actions creation/destruction Alexander Kozyrev
2022-02-19 4:11 ` [PATCH v7 00/10] ethdev: datapath-focused flow rules management Alexander Kozyrev
2022-02-19 4:11 ` [PATCH v7 01/11] ethdev: introduce flow engine configuration Alexander Kozyrev
2022-02-19 4:11 ` [PATCH v7 02/11] ethdev: add flow item/action templates Alexander Kozyrev
2022-02-19 4:11 ` [PATCH v7 03/11] ethdev: bring in async queue-based flow rules operations Alexander Kozyrev
2022-02-19 4:11 ` [PATCH v7 04/11] ethdev: bring in async indirect actions operations Alexander Kozyrev
2022-02-19 4:11 ` [PATCH v7 05/11] app/testpmd: add flow engine configuration Alexander Kozyrev
2022-02-19 4:11 ` [PATCH v7 06/11] app/testpmd: add flow template management Alexander Kozyrev
2022-02-19 4:11 ` [PATCH v7 07/11] app/testpmd: add flow table management Alexander Kozyrev
2022-02-19 4:11 ` [PATCH v7 08/11] app/testpmd: add async flow create/destroy operations Alexander Kozyrev
2022-02-19 4:11 ` [PATCH v7 09/11] app/testpmd: add flow queue push operation Alexander Kozyrev
2022-02-19 4:11 ` [PATCH v7 10/11] app/testpmd: add flow queue pull operation Alexander Kozyrev
2022-02-19 4:11 ` [PATCH v7 11/11] app/testpmd: add async indirect actions operations Alexander Kozyrev
2022-02-20 3:43 ` [PATCH v8 00/10] ethdev: datapath-focused flow rules management Alexander Kozyrev
2022-02-20 3:43 ` [PATCH v8 01/11] ethdev: introduce flow engine configuration Alexander Kozyrev
2022-02-21 9:47 ` Andrew Rybchenko
2022-02-21 9:52 ` Andrew Rybchenko
2022-02-21 12:53 ` Ori Kam
2022-02-21 14:33 ` Alexander Kozyrev
2022-02-21 14:53 ` Andrew Rybchenko
2022-02-21 15:49 ` Thomas Monjalon
2022-02-20 3:44 ` [PATCH v8 02/11] ethdev: add flow item/action templates Alexander Kozyrev
2022-02-21 10:57 ` Andrew Rybchenko
2022-02-21 13:12 ` Ori Kam
2022-02-21 15:05 ` Andrew Rybchenko [this message]
2022-02-21 15:43 ` Ori Kam
2022-02-21 15:14 ` Alexander Kozyrev
2022-02-20 3:44 ` [PATCH v8 03/11] ethdev: bring in async queue-based flow rules operations Alexander Kozyrev
2022-02-21 14:49 ` Andrew Rybchenko
2022-02-21 15:35 ` Alexander Kozyrev
2022-02-20 3:44 ` [PATCH v8 04/11] ethdev: bring in async indirect actions operations Alexander Kozyrev
2022-02-20 3:44 ` [PATCH v8 05/11] app/testpmd: add flow engine configuration Alexander Kozyrev
2022-02-20 3:44 ` [PATCH v8 06/11] app/testpmd: add flow template management Alexander Kozyrev
2022-02-20 3:44 ` [PATCH v8 07/11] app/testpmd: add flow table management Alexander Kozyrev
2022-02-20 3:44 ` [PATCH v8 08/11] app/testpmd: add async flow create/destroy operations Alexander Kozyrev
2022-02-20 3:44 ` [PATCH v8 09/11] app/testpmd: add flow queue push operation Alexander Kozyrev
2022-02-20 3:44 ` [PATCH v8 10/11] app/testpmd: add flow queue pull operation Alexander Kozyrev
2022-02-20 3:44 ` [PATCH v8 11/11] app/testpmd: add async indirect actions operations Alexander Kozyrev
2022-02-21 23:02 ` [PATCH v9 00/11] ethdev: datapath-focused flow rules management Alexander Kozyrev
2022-02-21 23:02 ` [PATCH v9 01/11] ethdev: introduce flow engine configuration Alexander Kozyrev
2022-02-21 23:02 ` [PATCH v9 02/11] ethdev: add flow item/action templates Alexander Kozyrev
2022-02-21 23:02 ` [PATCH v9 03/11] ethdev: bring in async queue-based flow rules operations Alexander Kozyrev
2022-02-21 23:02 ` [PATCH v9 04/11] ethdev: bring in async indirect actions operations Alexander Kozyrev
2022-02-21 23:02 ` [PATCH v9 05/11] app/testpmd: add flow engine configuration Alexander Kozyrev
2022-02-21 23:02 ` [PATCH v9 06/11] app/testpmd: add flow template management Alexander Kozyrev
2022-02-21 23:02 ` [PATCH v9 07/11] app/testpmd: add flow table management Alexander Kozyrev
2022-02-21 23:02 ` [PATCH v9 08/11] app/testpmd: add async flow create/destroy operations Alexander Kozyrev
2022-02-21 23:02 ` [PATCH v9 09/11] app/testpmd: add flow queue push operation Alexander Kozyrev
2022-02-21 23:02 ` [PATCH v9 10/11] app/testpmd: add flow queue pull operation Alexander Kozyrev
2022-02-21 23:02 ` [PATCH v9 11/11] app/testpmd: add async indirect actions operations Alexander Kozyrev
2022-02-23 3:02 ` [PATCH v10 00/11] ethdev: datapath-focused flow rules management Alexander Kozyrev
2022-02-23 3:02 ` [PATCH v10 01/11] ethdev: introduce flow engine configuration Alexander Kozyrev
2022-02-24 8:22 ` Andrew Rybchenko
2022-02-23 3:02 ` [PATCH v10 02/11] ethdev: add flow item/action templates Alexander Kozyrev
2022-02-24 8:34 ` Andrew Rybchenko
2022-02-23 3:02 ` [PATCH v10 03/11] ethdev: bring in async queue-based flow rules operations Alexander Kozyrev
2022-02-24 8:35 ` Andrew Rybchenko
2022-02-23 3:02 ` [PATCH v10 04/11] ethdev: bring in async indirect actions operations Alexander Kozyrev
2022-02-24 8:37 ` Andrew Rybchenko
2022-02-23 3:02 ` [PATCH v10 05/11] app/testpmd: add flow engine configuration Alexander Kozyrev
2022-02-23 3:02 ` [PATCH v10 06/11] app/testpmd: add flow template management Alexander Kozyrev
2022-02-23 3:02 ` [PATCH v10 07/11] app/testpmd: add flow table management Alexander Kozyrev
2022-02-23 3:02 ` [PATCH v10 08/11] app/testpmd: add async flow create/destroy operations Alexander Kozyrev
2022-02-23 3:02 ` [PATCH v10 09/11] app/testpmd: add flow queue push operation Alexander Kozyrev
2022-02-23 3:02 ` [PATCH v10 10/11] app/testpmd: add flow queue pull operation Alexander Kozyrev
2022-02-23 3:02 ` [PATCH v10 11/11] app/testpmd: add async indirect actions operations Alexander Kozyrev
2022-02-24 13:07 ` [PATCH v10 00/11] ethdev: datapath-focused flow rules management Ferruh Yigit
2022-02-24 13:13 ` Ferruh Yigit
2022-02-24 13:14 ` Raslan Darawsheh
2022-02-22 16:41 ` [PATCH v8 00/10] " Ferruh Yigit
2022-02-22 16:49 ` Ferruh Yigit
2021-10-06 4:48 [dpdk-dev] [RFC 0/3] " Alexander Kozyrev
2021-10-06 4:48 ` [dpdk-dev] [PATCH 1/3] ethdev: introduce flow pre-configuration hints Alexander Kozyrev
2021-10-13 4:11 ` Ajit Khaparde
2021-10-13 13:15 ` Ori Kam
2021-10-31 17:27 ` Ajit Khaparde
2021-11-01 10:40 ` Ori Kam
2021-10-06 4:48 ` [dpdk-dev] [PATCH 2/3] ethdev: add flow item/action templates Alexander Kozyrev
2021-10-06 17:24 ` Ivan Malov
2021-10-13 1:25 ` Alexander Kozyrev
2021-10-13 2:26 ` Ajit Khaparde
2021-10-13 2:38 ` Alexander Kozyrev
2021-10-13 11:25 ` Ivan Malov
2021-10-06 4:48 ` [dpdk-dev] [PATCH 3/3] ethdev: add async queue-based flow rules operations Alexander Kozyrev
2021-10-06 16:24 ` Ivan Malov
2021-10-13 1:10 ` Alexander Kozyrev
2021-10-13 4:57 ` Ajit Khaparde
2021-10-13 13:17 ` Ori Kam
2022-01-18 15:30 ` [PATCH v2 00/10] ethdev: datapath-focused flow rules management Alexander Kozyrev
2022-01-18 15:30 ` [PATCH v2 01/10] ethdev: introduce flow pre-configuration hints Alexander Kozyrev
2022-01-24 14:36 ` Jerin Jacob
2022-01-24 17:35 ` Thomas Monjalon
2022-01-24 17:46 ` Jerin Jacob
2022-01-24 18:08 ` Bruce Richardson
2022-01-25 1:14 ` Alexander Kozyrev
2022-01-25 15:58 ` Ori Kam
2022-01-25 18:09 ` Bruce Richardson
2022-01-25 18:14 ` Bruce Richardson
2022-01-26 9:45 ` Ori Kam
2022-01-26 10:52 ` Bruce Richardson
2022-01-26 11:21 ` Thomas Monjalon
2022-01-26 12:19 ` Ori Kam
2022-01-26 13:41 ` Bruce Richardson
2022-01-26 15:12 ` Ori Kam
2022-01-24 17:40 ` Ajit Khaparde
2022-01-25 1:28 ` Alexander Kozyrev
2022-01-25 18:44 ` Jerin Jacob
2022-01-26 22:02 ` Alexander Kozyrev
2022-01-27 9:34 ` Jerin Jacob
2022-01-18 15:30 ` [PATCH v2 02/10] ethdev: add flow item/action templates Alexander Kozyrev
2022-01-18 15:30 ` [PATCH v2 03/10] ethdev: bring in async queue-based flow rules operations Alexander Kozyrev
2022-01-18 15:30 ` [PATCH v2 04/10] app/testpmd: implement rte flow configure Alexander Kozyrev
2022-01-18 15:33 ` [v2,05/10] app/testpmd: implement rte flow item/action template Alexander Kozyrev
2022-01-18 15:34 ` [v2,06/10] app/testpmd: implement rte flow table Alexander Kozyrev
2022-01-18 15:35 ` [v2,07/10] app/testpmd: implement rte flow queue create flow Alexander Kozyrev
2022-01-18 15:35 ` [v2,08/10] app/testpmd: implement rte flow queue drain Alexander Kozyrev
2022-01-18 15:36 ` [v2,09/10] app/testpmd: implement rte flow queue dequeue Alexander Kozyrev
2022-01-18 15:37 ` [v2,10/10] app/testpmd: implement rte flow queue indirect action Alexander Kozyrev
2022-01-19 7:16 ` [PATCH v2 00/10] ethdev: datapath-focused flow rules management Suanming Mou
2022-01-24 15:10 ` Ori Kam
2022-02-06 3:25 ` [PATCH v3 " Alexander Kozyrev
2022-02-06 3:25 ` [PATCH v3 01/10] ethdev: introduce flow pre-configuration hints Alexander Kozyrev
2022-02-07 13:15 ` Ori Kam
2022-02-07 14:52 ` Jerin Jacob
2022-02-07 17:59 ` Alexander Kozyrev
2022-02-07 18:24 ` Jerin Jacob
2022-02-06 3:25 ` [PATCH v3 02/10] ethdev: add flow item/action templates Alexander Kozyrev
2022-02-07 13:16 ` Ori Kam
2022-02-06 3:25 ` [PATCH v3 03/10] ethdev: bring in async queue-based flow rules operations Alexander Kozyrev
2022-02-07 13:18 ` Ori Kam
2022-02-08 10:56 ` Jerin Jacob
2022-02-08 14:11 ` Alexander Kozyrev
2022-02-08 15:23 ` Ivan Malov
2022-02-09 5:40 ` Alexander Kozyrev
2022-02-08 17:36 ` Jerin Jacob
2022-02-09 5:50 ` Jerin Jacob
2022-02-06 3:25 ` [PATCH v3 04/10] app/testpmd: implement rte flow configuration Alexander Kozyrev
2022-02-07 13:19 ` Ori Kam
2022-02-06 3:25 ` [PATCH v3 05/10] app/testpmd: implement rte flow template management Alexander Kozyrev
2022-02-07 13:20 ` Ori Kam
2022-02-06 3:25 ` [PATCH v3 06/10] app/testpmd: implement rte flow table management Alexander Kozyrev
2022-02-07 13:22 ` Ori Kam
2022-02-06 3:25 ` [PATCH v3 07/10] app/testpmd: implement rte flow queue flow operations Alexander Kozyrev
2022-02-07 13:21 ` Ori Kam
2022-02-06 3:25 ` [PATCH v3 08/10] app/testpmd: implement rte flow push operations Alexander Kozyrev
2022-02-07 13:22 ` Ori Kam
2022-02-06 3:25 ` [PATCH v3 09/10] app/testpmd: implement rte flow pull operations Alexander Kozyrev
2022-02-07 13:23 ` Ori Kam
2022-02-06 3:25 ` [PATCH v3 10/10] app/testpmd: implement rte flow queue indirect actions Alexander Kozyrev
2022-02-07 13:23 ` Ori Kam
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=5d8e0b32-f674-a43f-20ee-a689ab7c2012@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=ajit.khaparde@broadcom.com \
--cc=akozyrev@nvidia.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=ivan.malov@oktetlabs.ru \
--cc=jerinj@marvell.com \
--cc=mohammad.abdul.awal@intel.com \
--cc=orika@nvidia.com \
--cc=qi.z.zhang@intel.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).