RTE_FLOW_ACTION_VXLAN_ENCAP(3)
π NAME π
rte_flow_action_vxlan_encap β bestie, this is the struct you reach for when you wanna wrap your traffic up in a whole VXLAN tunnel like it's a lil gift π
So this page lives in the Library Functions Manual, and it's all about one struct and one field, no cap.
β¨ SYNOPSIS β¨
Pull it in like this:
#include <rte_flow.h>
π Data Fields
struct rte_flow_item * definition
π¦ Detailed Description π¦
β οΈ Warning β EXPERIMENTAL: this structure may change without prior notice. Translating: it's giving "we might redraw the blueprint at any moment", so don't get too attached, bestie π
RTE_FLOW_ACTION_TYPE_VXLAN_ENCAP β the action that does VXLAN tunnel end-point encapsulation π
This struct is the data definition for that VXLAN tunnel end-point encapsulation. Yeah.
So here's the tea β: you don't hand over the tunnel definition directly β it comes through the flow item pattern. And that pattern you provide must conform to RFC7348 for the tunnel you're specifying. RFC7348, periodt, no exceptions π
You also gotta give the flow definition in order, starting from the RTE_FLOW_ITEM_TYPE_ETH definition and going all the way up to the end item, which is specified by RTE_FLOW_ITEM_TYPE_END. Start to end, in order, no skipping around like it's a playlist on shuffle π§
Then there's the mask field. It's the icon that lets you say which fields in your flow item definitions can be ignored, and which ones actually hold valid data and can be used verbatim. She's the vibe check for your fields π
π Note: the last field is not used in the definition of a tunnel and can be ignored. Just leaving it there like a decorative throw pillow ποΈ
Valid flow definitions for RTE_FLOW_ACTION_TYPE_VXLAN_ENCAP include, and these are iconic:
- ETH / IPV4 / UDP / VXLAN / END
- ETH / IPV6 / UDP / VXLAN / END
- ETH / VLAN / IPV4 / UDP / VXLAN / END
Definition at line 3700 of file rte_flow.h. π
πΈ Field Documentation πΈ
π«Ά struct rte_flow_item* definition
Encapsulating vxlan tunnel definition (terminated by the END pattern item). So yes, when you're done listing your stuff, END shuts the door behind you πͺβ¨
Definition at line 3705 of file rte_flow.h. π
π Author π
Generated automatically by Doxygen for DPDK from the source code. Not a human, just a very busy lil robot π€π
Okay that's the whole page, bestie, you ate it up π This was DPDK, Version 25.11.3, from the Library Functions Manual, mwah, go forth and encapsulate responsibly π π
π¦ where this page comes from
- ubuntu resolute: dpdk-doc 25.11.3-0ubuntu0.26.04.1 Β· BSD-3-Clause
- ubuntu stonking: dpdk-doc 25.11.3-1 Β· BSD-3-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms