RTE_ETH_FLEX_PAYLOAD_CFG(3)

✨ NAME ✨

rte_eth_flex_payload_cfg β€” bestie, it's a struct πŸ’… from the DPDK Library Functions Manual, section 3, and she's here to help you pick which bytes get yanked out of your protocol layers and yeeted into the flexible payload for filtering πŸŽ€


🌸 SYNOPSIS 🌸

#include <rte_eth_ctrl.h>

πŸ¦‹ Data Fields

  • enum rte_eth_payload_type type
  • uint16_t src_offset [RTE_ETH_FDIR_MAX_FLEXLEN]

πŸ’– Detailed Description πŸ’–

okay so. this is a structure used to select bytes extracted from the protocol layers to flexible payload for filter. that's her whole job, no cap.

she lives at Definition at line 386 of file rte_eth_ctrl.h. πŸ“


πŸ‘‘ Field Documentation πŸ‘‘

✨ enum rte_eth_payload_type type

literally just the payload type, bestie. that's the vibe. 🫢

Definition at line 387 of file rte_eth_ctrl.h.

🌈 uint16_t src_offset[RTE_ETH_FDIR_MAX_FLEXLEN]

so this one is the offset in bytes from the beginning of packet's payload. and src_offset[i]? that tells you flexbyte i's offset in the original packet payload β€” like a lil map of where each flexbyte came from in the source packet πŸ—ΊοΈβœ¨

⚠️ important, bestie: this value should be less than flex_payload_limit in struct rte_eth_fdir_info. do not skip that. it's giving boundary conditions and we respect her πŸ’€

Definition at line 388 of file rte_eth_ctrl.h.


πŸŽ€ Author πŸŽ€

Generated automatically by Doxygen for DPDK from the source code. she was born from the tooling, not from human hands, and honestly? iconic πŸ€–πŸ’–


and that's the whole page, bestie!! this was DPDK Version 25.11.3, filed under rte_eth_flex_payload_cfg(3) β€” mwah, slay, go configure some payloads, ily πŸ«ΆπŸ’…πŸŒŸ

πŸ“¦ where this page comes from