Add new flow action types for GENEVE tunnel manipulation: 1. RTE_FLOW_ACTION_TYPE_GENEVE_ENCAP - For encapsulating packets into GENEVE tunnels 2. RTE_FLOW_ACTION_TYPE_GENEVE_DECAP - For decapsulating packets from GENEVE tunnels 3. struct rte_flow_action_geneve_encap - Data structure to define tunnel encapsulation parameters
These actions allow users to build more flexible network virtualization solutions using GENEVE tunnels as specified by RFC8926. Signed-off-by: Sunyang Wu <[email protected]> --- lib/ethdev/rte_flow.h | 50 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) diff --git a/lib/ethdev/rte_flow.h b/lib/ethdev/rte_flow.h index 3d2ccdeb92..fc03489511 100644 --- a/lib/ethdev/rte_flow.h +++ b/lib/ethdev/rte_flow.h @@ -2825,6 +2825,23 @@ enum rte_flow_action_type { */ RTE_FLOW_ACTION_TYPE_NVGRE_DECAP, + /** + * Encapsulate flow in GENEVE tunnel defined in the + * rte_flow_action_geneve_encap action structure. + * + * See struct rte_flow_action_geneve_encap. + */ + RTE_FLOW_ACTION_TYPE_GENEVE_ENCAP, + + /** + * Decapsulate outer most GENEVE tunnel from matched flow. + * + * If flow pattern does not define a valid GENEVE tunnel (as specified by + * RFC8296) then the PMD should return a RTE_FLOW_ERROR_TYPE_ACTION + * error. + */ + RTE_FLOW_ACTION_TYPE_GENEVE_DECAP, + /** * Add outer header whose template is provided in its data buffer * @@ -3738,6 +3755,39 @@ struct rte_flow_action_nvgre_encap { struct rte_flow_item *definition; }; +/** + * @warning + * @b EXPERIMENTAL: this structure may change without prior notice + * + * RTE_FLOW_ACTION_TYPE_GENEVE_ENCAP + * + * GENEVE tunnel end-point encapsulation data definition + * + * The tunnel definition is provided through the flow item pattern the + * provided pattern must conform with RFC8926. The flow definition must be + * provided in order from the RTE_FLOW_ITEM_TYPE_ETH definition up the end item + * which is specified by RTE_FLOW_ITEM_TYPE_END. + * + * The mask field allows user to specify which fields in the flow item + * definitions can be ignored and which have valid data and can be used + * verbatim. + * + * Note: the last field is not used in the definition of a tunnel and can be + * ignored. + * + * Valid flow definition for RTE_FLOW_ACTION_TYPE_GENEVE_ENCAP include: + * + * - ETH / IPV4 / GENEVE / END + * - ETH / VLAN / IPV6 / GENEVE / END + */ +struct rte_flow_action_geneve_encap { + /** + * Encapsulating geneve tunnel definition + * (terminated by the END pattern item). + */ + struct rte_flow_item *definition; +}; + /** * @warning * @b EXPERIMENTAL: this structure may change without prior notice -- 2.19.0.rc0.windows.1
