rte_eth_tunnel_flow(3)

💅 rte_eth_tunnel_flow — the manual page, but make it make sense

okay so bestie, you opened rte_eth_tunnel_flow(3) and the man page is giving nothing — just vibes and struct fields. don't worry, i got you. this is a structure (a lil C struct, not a function, iykyk) and it lives in the DPDK library functions manuals. let's get into it ✨

---

🎀 SYNOPSIS

pull it in like this, periodt:

#include <rte_eth_ctrl.h>

🌸 Data Fields

these are the three fields doing all the work, no cap:

• enum rte_eth_fdir_tunnel_type tunnel_type — the tunnel type you're tryna match
• uint32_t tunnel_id — the tunnel ID you're tryna match
• struct rte_ether_addr mac_addr — the MAC address you're tryna match

---

🦋 Detailed Description

so this struct is literally the input for tunnel flow. and when the page says tunnel, rn it's talking VxLAN or NVGRE — that's it, that's the list 💅

the page also drops the receipts: Definition at line 257 of file rte_eth_ctrl.h.

---

🔥 Field Documentation

⭐ enum rte_eth_fdir_tunnel_type tunnel_type

the tunnel type to match. that's the whole assignment, bestie 🫶

Definition at line 258 of file rte_eth_ctrl.h.

⭐ uint32_t tunnel_id

the tunnel ID to match — like TNI, VNI... and yes, it's in big endian, so don't come crying to me when your bytes are backwards 💀

Definition at line 260 of file rte_eth_ctrl.h.

⭐ struct rte_ether_addr mac_addr

the MAC address to match. iconic, essential, no notes 🌈

Definition at line 261 of file rte_eth_ctrl.h.

---

👑 Author

generated automatically by Doxygen for DPDK, straight from the source code. not me, not you — Doxygen did that 🙈

---

reminder bestie: every single one of these is a match condition. tunnel_type, tunnel_id, mac_addr — all "to match". the struct is just out here collecting criteria like it's a group chat invite list 💜

---

okay that's the whole page, you're basically a DPDK girlie now 🧚

signing off with the official deets: this is the rte_eth_tunnel_flow(3) page, from DPDK Version 26.03.0 — mwah, slay, bye 💅🎀