rte_eth_tunnel_flow(3)

✨ rte_eth_tunnel_flow ✨

ok so bestie, you know how sometimes you just need a whole struct to describe a tunnel flow? yeah. that's this. it lives in the rte_eth_ctrl.h header β€” a 3-section-of-the-manual kinda deal, full library-functions-manual energy πŸ’…


🌸 SYNOPSIS 🌸

#include <rte_eth_ctrl.h>

πŸŽ€ Data Fields

  • enum rte_eth_fdir_tunnel_type tunnel_type
  • uint32_t tunnel_id
  • struct rte_ether_addr mac_addr

πŸ’– Detailed Description πŸ’–

It's a struct, and its whole job is defining the input for a tunnel flow. rn it's doing VxLAN or NVGRE β€” that's the vibe, those are the two, no cap.

Definition at line 257 of file rte_eth_ctrl.h.


πŸ¦‹ Field Documentation πŸ¦‹

⭐ enum rte_eth_fdir_tunnel_type tunnel_type

the tunnel type you wanna match on. literally just that.

Definition at line 258 of file rte_eth_ctrl.h.

⭐ uint32_t tunnel_id

the tunnel ID you're matching β€” TNI, VNI... whatever your tunnel situation is calling it 🫢. and she's in big endian, so don't come at her with little-endian bytes, she will not be matching correctly and that's on you bestie 😭.

Definition at line 260 of file rte_eth_ctrl.h.

⭐ struct rte_ether_addr mac_addr

the MAC address to match. iconic little ethernet address, doing her thing ✨

Definition at line 261 of file rte_eth_ctrl.h.


πŸ‘‘ Author πŸ‘‘

Generated automatically by Doxygen for DPDK from the source code. not a human author, just a lil doc generator doing its thing, and honestly? it ate πŸ’€


k bye bestie, go match some tunnels πŸ’œ β€” this was DPDK Version 25.11.3, page rte_eth_tunnel_flow(3), slay πŸŽ€

πŸ“¦ where this page comes from