From: Alexander Kozyrev <akozyrev@nvidia.com>
To: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Ori Kam <orika@nvidia.com>,
"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 v5 01/10] ethdev: introduce flow pre-configuration hints
Date: Wed, 16 Feb 2022 22:17:30 +0000 [thread overview]
Message-ID: <DM5PR12MB2405270AA367D9F4C19117F4AF359@DM5PR12MB2405.namprd12.prod.outlook.com> (raw)
In-Reply-To: <982e92be-5e58-7e63-4bf4-7f095e45fcbd@oktetlabs.ru>
On Wed, Feb 16, 2022 8:03 Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>:
> On 2/11/22 21:47, Alexander Kozyrev wrote:
> > On Friday, February 11, 2022 5:17 Andrew Rybchenko
> <andrew.rybchenko@oktetlabs.ru> wrote:
> >> Sent: Friday, February 11, 2022 5:17
> >> To: Alexander Kozyrev <akozyrev@nvidia.com>; dev@dpdk.org
> >> Cc: Ori Kam <orika@nvidia.com>; NBU-Contact-Thomas Monjalon
> (EXTERNAL)
> >> <thomas@monjalon.net>; ivan.malov@oktetlabs.ru;
> ferruh.yigit@intel.com;
> >> mohammad.abdul.awal@intel.com; qi.z.zhang@intel.com;
> jerinj@marvell.com;
> >> ajit.khaparde@broadcom.com; bruce.richardson@intel.com
> >> Subject: Re: [PATCH v5 01/10] ethdev: introduce flow pre-configuration
> hints
> >>
> >> On 2/11/22 05:26, Alexander Kozyrev wrote:
> >>> The flow rules creation/destruction at a large scale incurs a performance
> >>> penalty and may negatively impact the packet processing when used
> >>> as part of the datapath logic. This is mainly because software/hardware
> >>> resources are allocated and prepared during the flow rule creation.
> >>>
> >>> In order to optimize the insertion rate, PMD may use some hints
> provided
> >>> by the application at the initialization phase. The rte_flow_configure()
> >>> function allows to pre-allocate all the needed resources beforehand.
> >>> These resources can be used at a later stage without costly allocations.
> >>> Every PMD may use only the subset of hints and ignore unused ones or
> >>> fail in case the requested configuration is not supported.
> >>>
> >>> The rte_flow_info_get() is available to retrieve the information about
> >>> supported pre-configurable resources. Both these functions must be
> called
> >>> before any other usage of the flow API engine.
> >>>
> >>> Signed-off-by: Alexander Kozyrev <akozyrev@nvidia.com>
> >>> Acked-by: Ori Kam <orika@nvidia.com>
>
> [snip]
>
> >>> diff --git a/lib/ethdev/rte_flow.c b/lib/ethdev/rte_flow.c
> >>> index a93f68abbc..66614ae29b 100644
> >>> --- a/lib/ethdev/rte_flow.c
> >>> +++ b/lib/ethdev/rte_flow.c
> >>> @@ -1391,3 +1391,43 @@ rte_flow_flex_item_release(uint16_t port_id,
> >>> ret = ops->flex_item_release(dev, handle, error);
> >>> return flow_err(port_id, ret, error);
> >>> }
> >>> +
> >>> +int
> >>> +rte_flow_info_get(uint16_t port_id,
> >>> + struct rte_flow_port_info *port_info,
> >>> + 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(!ops))
> >>> + return -rte_errno;
> >>> + if (likely(!!ops->info_get)) {
> >>
> >> expected ethdev state must be validated. Just configured?
> >>
> >>> + return flow_err(port_id,
> >>> + ops->info_get(dev, port_info, error),
> >>
> >> port_info must be checked vs NULL
> >
> > We don’t have any NULL checks for parameters in the whole ret flow API
> library.
> > See rte_flow_create() for example. attributes, pattern and actions are
> passed to PMD unchecked.
>
> IMHO it is hardly a good reason to have no such check here.
> The API is pure control path. So, it must validate all input
> arguments and it is better to do it in a generic place.
Agree, I have no objections to introduce these validation checks on control path.
My only concern is the data-path performance, so I'm reluctant to add them to
rte_flow_q_create/destroy functions. But let's add NULL checks to configuration
routines, ok?
> >>> + error);
> >>> + }
> >>> + return rte_flow_error_set(error, ENOTSUP,
> >>> + RTE_FLOW_ERROR_TYPE_UNSPECIFIED,
> >>> + NULL, rte_strerror(ENOTSUP));
> >>> +}
> >>> +
> >>> +int
> >>> +rte_flow_configure(uint16_t port_id,
> >>> + const struct rte_flow_port_attr *port_attr,
> >>> + 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(!ops))
> >>> + return -rte_errno;
> >>> + if (likely(!!ops->configure)) {
> >>
> >> The API must validate ethdev state. configured and not started?
> > Again, we have no such validation for any rte flow API today.
>
> Same here. If documentation defines in which state the API
> should be called, generic code must guarantee it.
Ok, as long as it stays in the configuration phase only.
> >>
> >>> + return flow_err(port_id,
> >>> + ops->configure(dev, port_attr, error),
> >>
> >> port_attr must be checked vs NULL
> > Same.
> >
> >>> + 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 1031fb246b..92be2a9a89 100644
> >>> --- a/lib/ethdev/rte_flow.h
> >>> +++ b/lib/ethdev/rte_flow.h
> >>> @@ -4853,6 +4853,114 @@ rte_flow_flex_item_release(uint16_t
> port_id,
> >>> const struct rte_flow_item_flex_handle *handle,
> >>> struct rte_flow_error *error);
> >>>
> >>> +/**
> >>> + * @warning
> >>> + * @b EXPERIMENTAL: this API may change without prior notice.
> >>> + *
> >>> + * Information about available pre-configurable resources.
> >>> + * The zero value means a resource cannot be pre-allocated.
> >>> + *
> >>> + */
> >>> +struct rte_flow_port_info {
> >>> + /**
> >>> + * Number of pre-configurable counter actions.
> >>> + * @see RTE_FLOW_ACTION_TYPE_COUNT
> >>> + */
> >>> + uint32_t nb_counters;
> >>
> >> Name says that it is a number of counters, but description
> >> says that it is about actions.
> >> Also I don't understand what does "pre-configurable" mean.
> >> Isn't it a maximum number of available counters?
> >> If no, how can I find a maximum?
> > It is number of pre-allocated and pre-configured actions.
> > How are they pr-configured is up to PDM driver.
> > But let's change to "pre-configured" everywhere.
> > Configuration includes some memory allocation anyway.
>
> Sorry, but I still don't understand. I guess HW has
> a hard limit on a number of counters. How can I get
> the information?
Sorry for not being clear. These are resources/objects limitation.
It may be the hard HW limit on number of counter objects, for example.
Or the system has a little of memory and NIC is constrained in memory
in its attempt to create these counter objects as another example.
In any case, the info_get() API should return the limit to a user.
> >>
> >>> + /**
> >>> + * Number of pre-configurable aging flows actions.
> >>> + * @see RTE_FLOW_ACTION_TYPE_AGE
> >>> + */
> >>> + uint32_t nb_aging_flows;
> >>
> >> Same
> > Ditto.
> >
> >>> + /**
> >>> + * Number of pre-configurable traffic metering actions.
> >>> + * @see RTE_FLOW_ACTION_TYPE_METER
> >>> + */
> >>> + uint32_t nb_meters;
> >>
> >> Same
> > Ditto.
> >
> >>> +};
> >>> +
> >>> +/**
> >>> + * @warning
> >>> + * @b EXPERIMENTAL: this API may change without prior notice.
> >>> + *
> >>> + * Retrieve configuration attributes supported by the port.
> >>
> >> Description should be a bit more flow API aware.
> >> Right now it sounds too generic.
> > Ok, how about
> > "Get information about flow engine pre-configurable resources."
> >
> >>> + *
> >>> + * @param port_id
> >>> + * Port identifier of Ethernet device.
> >>> + * @param[out] port_info
> >>> + * A pointer to a structure of type *rte_flow_port_info*
> >>> + * to be filled with the contextual information of the port.
> >>> + * @param[out] error
> >>> + * Perform verbose error reporting if not NULL.
> >>> + * PMDs initialize this structure in case of error only.
> >>> + *
> >>> + * @return
> >>> + * 0 on success, a negative errno value otherwise and rte_errno is set.
> >>> + */
> >>> +__rte_experimental
> >>> +int
> >>> +rte_flow_info_get(uint16_t port_id,
> >>> + struct rte_flow_port_info *port_info,
> >>> + struct rte_flow_error *error);
> >>> +
> >>> +/**
> >>> + * @warning
> >>> + * @b EXPERIMENTAL: this API may change without prior notice.
> >>> + *
> >>> + * Resource pre-allocation and pre-configuration settings.
> >>
> >> What is the difference between pre-allocation and pre-configuration?
> >> Why are both mentioned above, but just pre-configured actions are
> >> mentioned below?
> > Please see answer to this question above.
> >
> >>> + * The zero value means on demand resource allocations only.
> >>> + *
> >>> + */
> >>> +struct rte_flow_port_attr {
> >>> + /**
> >>> + * Number of counter actions pre-configured.
> >>> + * @see RTE_FLOW_ACTION_TYPE_COUNT
> >>> + */
> >>> + uint32_t nb_counters;
> >>> + /**
> >>> + * Number of aging flows actions pre-configured.
> >>> + * @see RTE_FLOW_ACTION_TYPE_AGE
> >>> + */
> >>> + uint32_t nb_aging_flows;
> >>> + /**
> >>> + * Number of traffic metering actions pre-configured.
> >>> + * @see RTE_FLOW_ACTION_TYPE_METER
> >>> + */
> >>> + uint32_t nb_meters;
> >>> +};
> >>> +
> >>> +/**
> >>> + * @warning
> >>> + * @b EXPERIMENTAL: this API may change without prior notice.
> >>> + *
> >>> + * Configure the port's flow API engine.
> >>> + *
> >>> + * This API can only be invoked before the application
> >>> + * starts using the rest of the flow library functions.
> >>> + *
> >>> + * The API can be invoked multiple times to change the
> >>> + * settings. The port, however, may reject the changes.
> >>> + *
> >>> + * Parameters in configuration attributes must not exceed
> >>> + * numbers of resources returned by the rte_flow_info_get API.
> >>> + *
> >>> + * @param port_id
> >>> + * Port identifier of Ethernet device.
> >>> + * @param[in] port_attr
> >>> + * Port configuration attributes.
> >>> + * @param[out] error
> >>> + * Perform verbose error reporting if not NULL.
> >>> + * PMDs initialize this structure in case of error only.
> >>> + *
> >>> + * @return
> >>> + * 0 on success, a negative errno value otherwise and rte_errno is set.
> >>> + */
> >>> +__rte_experimental
> >>> +int
> >>> +rte_flow_configure(uint16_t port_id,
> >>> + const struct rte_flow_port_attr *port_attr,
> >>> + struct rte_flow_error *error);
> >>> +
> >>> #ifdef __cplusplus
> >>> }
> >>> #endif
>
> [snip]
next prev parent reply other threads:[~2022-02-16 22:17 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 [this message]
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
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=DM5PR12MB2405270AA367D9F4C19117F4AF359@DM5PR12MB2405.namprd12.prod.outlook.com \
--to=akozyrev@nvidia.com \
--cc=ajit.khaparde@broadcom.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--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).