rte_table_...inq_params(3)

πŸŽ€ NAME πŸŽ€

rte_table_action_encap_qinq_params β€” bestie, it's the QinQ encap parameters struct, and yes she's exactly what she sounds like πŸ’…


✨ SYNOPSIS ✨

#include <rte_table_action.h>

πŸ¦‹ Data Fields πŸ¦‹

  • struct rte_table_action_ether_hdr ether
  • struct rte_table_action_vlan_hdr svlan
  • struct rte_table_action_vlan_hdr cvlan

πŸ’– Detailed Description πŸ’–

Okay so. This is the QinQ encap parameters struct. That's the whole vibe. It's giving "I hold the stuff you need to stack VLANs on top of each other" and honestly? Iconic. πŸ‘‘

Lowkey the most important thing here: this bad boy is defined at line 453 of file rte_table_action.h. So if you ever get lost, that's where she lives. 🏠


🌸 Field Documentation 🌸

  • struct rte_table_action_ether_hdr ether β€” the Ethernet header. That's it, that's the whole job. The outer layer, the moment before the VLANs show up. Defined at line 454 of file rte_table_action.h. πŸ“
  • struct rte_table_action_vlan_hdr svlan β€” the Service VLAN header. The S in SVLAN. The outer tag, the one doing main character energy on the top of the stack. Defined at line 455 of file rte_table_action.h. ✨
  • struct rte_table_action_vlan_hdr cvlan β€” the Customer VLAN header. The C. The inner tag, tucked inside the SVLAN like a lil secret. Together with svlan she is literally the entire point of QinQ. Defined at line 456 of file rte_table_action.h. 🫢
No cap, three fields, three line numbers, that's the whole struct. Simple, clean, slays. πŸ’…

πŸ‘‘ Author πŸ‘‘

Generated automatically by Doxygen for DPDK from the source code. So like… not a human, a robot wrote this, and honestly the robot ate. πŸ€–β­


That's the page, bestie β€” DPDK, Version 25.11.3, and the whole thing is from the rte_table_...inq_params(3) manual. Go forth and encapsulate. πŸŒˆπŸ’–

πŸ“¦ where this page comes from