725e515ed1
The rte_security API which enables inline protocol/crypto feature mandates that for every security session an rte_flow is created. This would internally translate to a rule in the hardware which would do packet classification. In rte_security, one SA would be one security session. And if an rte_flow need to be created for every session, the number of SAs supported by an inline implementation would be limited by the number of rte_flows the PMD would be able to support. If the fields SPI & IP addresses are allowed to be a range, then this limitation can be overcome. Multiple flows will be able to use one rule for SECURITY processing. In this case, the security session provided as conf would be NULL. Application should do an rte_flow_validate() to make sure the flow is supported on the PMD. Signed-off-by: Anoob Joseph <anoobj@marvell.com> Reviewed-by: Jerin Jacob <jerinj@marvell.com> Acked-by: Ori Kam <orika@mellanox.com> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com> Acked-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com> |
||
|---|---|---|
| .. | ||
| ethdev_private.c | ||
| ethdev_private.h | ||
| ethdev_profile.c | ||
| ethdev_profile.h | ||
| Makefile | ||
| meson.build | ||
| rte_class_eth.c | ||
| rte_dev_info.h | ||
| rte_eth_ctrl.h | ||
| rte_ethdev_core.h | ||
| rte_ethdev_driver.h | ||
| rte_ethdev_pci.h | ||
| rte_ethdev_vdev.h | ||
| rte_ethdev_version.map | ||
| rte_ethdev.c | ||
| rte_ethdev.h | ||
| rte_flow_driver.h | ||
| rte_flow.c | ||
| rte_flow.h | ||
| rte_mtr_driver.h | ||
| rte_mtr.c | ||
| rte_mtr.h | ||
| rte_tm_driver.h | ||
| rte_tm.c | ||
| rte_tm.h | ||