*/
RTE_FLOW_ITEM_TYPE_L2TPV3OIP,
+ /**
+ * Matches PFCP Header.
+ * See struct rte_flow_item_pfcp.
+ *
+ */
+ RTE_FLOW_ITEM_TYPE_PFCP,
+
};
/**
};
#endif
+/**
+ * @warning
+ * @b EXPERIMENTAL: this structure may change without prior notice
+ *
+ * RTE_FLOW_ITEM_TYPE_PFCP
+ *
+ * Match PFCP Header
+ */
+struct rte_flow_item_pfcp {
+ uint8_t s_field;
+ uint8_t msg_type;
+ rte_be16_t msg_len;
+ rte_be64_t seid;
+};
+
+/** Default mask for RTE_FLOW_ITEM_TYPE_PFCP. */
+#ifndef __cplusplus
+static const struct rte_flow_item_pfcp rte_flow_item_pfcp_mask = {
+ .s_field = 0x01,
+ .seid = RTE_BE64(0xffffffffffffffff),
+};
+#endif
+
/**
* Matching pattern item definition.
*
* direction.
*
* Multiple flows can be configured to use the same security session.
+ *
+ * The NULL value is allowed for security session. If security session is NULL,
+ * then SPI field in ESP flow item and IP addresses in flow items 'IPv4' and
+ * 'IPv6' will be allowed to be a range. The rule thus created can enable
+ * security processing on multiple flows.
*/
struct rte_flow_action_security {
void *security_session; /**< Pointer to security session structure. */