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 etherstruct rte_table_action_vlan_hdr svlanstruct 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 filerte_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 filerte_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 withsvlanshe is literally the entire point of QinQ. Defined at line 456 of filerte_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
- 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