RTE_FLOW_ACTION_IPV6_EXT_PUSH(3)

πŸ’– NAME πŸ’–

rte_flow_action_ipv6_ext_push β€” bestie, it's the struct that describes shoving a brand-new IPv6 extension header onto a packet, and it lives in the rte_flow_a...v6_ext_push(3) manual page, section 3, library functions, periodt.


✨ SYNOPSIS ✨

#include <rte_flow.h>

πŸŽ€ Data Fields

  • uint8_t * data
  • size_t size
  • uint8_t type

🌸 Detailed Description 🌸

⚠️ Warning β€” EXPERIMENTAL: this structure may change without prior notice. No cap, it could just... transform on you. Guard your heart and your ABI. πŸ’€

RTE_FLOW_ACTION_TYPE_IPV6_EXT_PUSH

The valid flow definition for RTE_FLOW_ACTION_TYPE_IPV6_EXT_PUSH include:

  • IPV6_EXT TYPE / IPV6_EXT_HEADER_IN_TYPE / END

The data must be added as the last IPv6 extension. It's giving "last one in, no cutting the line" energy β€” the extension goes at the very end, okay? 🫢

Definition at line 3828 of file rte_flow.h.


πŸ¦‹ Field Documentation πŸ¦‹

πŸ’… uint8_t* data

IPv6 extension header data. Literally the payload of your extension header, the whole point of the vibe. ✨

Definition at line 3829 of file rte_flow.h.

πŸ’… size_t size

Size (in bytes) of data. How much of it there is, measured in bytes, iconic. πŸ“

Definition at line 3830 of file rte_flow.h.

πŸ’… uint8_t type

Type of IPv6 extension. This is the little label that tells everyone which extension it is. πŸ‘‘

Definition at line 3831 of file rte_flow.h.


🌈 Author 🌈

Generated automatically by Doxygen for DPDK from the source code. Not a human author, just the machine doing its thing, slay. πŸ€–πŸ’–


And that's the whole page, bestie β€” this doc is DPDK Version 25.11.3, it's the rte_flow_a...v6_ext_push(3) page, and it said all of this on its date stamp. Mwah, go forth and push IPv6 extensions responsibly. πŸ’…βœ¨

πŸ“¦ where this page comes from