rte_table_...pv6_header(3)

πŸ’– NAME πŸ’–

rte_table_action_ipv6_header β€” bestie, it's the struct that holds your pre-baked IPv6 header fields πŸ’…


✨ SYNOPSIS ✨

#include <rte_table_action.h>

🌸 Data Fields 🌸

  • struct rte_ipv6_addr sa
  • struct rte_ipv6_addr da
  • uint32_t flow_label
  • uint8_t dscp
  • uint8_t hop_limit

πŸ¦‹ Detailed Description πŸ¦‹

Pre-computed IPv6 header fields for encapsulation action.

It's giving "I already did the math, just wrap the packet" ✨ no cap.

Definition at line 422 of file rte_table_action.h.


πŸŽ€ Field Documentation πŸŽ€

πŸ’œ struct rte_ipv6_addr sa

Source address. That's where it's coming from, mkay 🫢

Definition at line 423 of file rte_table_action.h.

πŸ’œ struct rte_ipv6_addr da

Destination address. Where it's headed, main character energy, it knows its destination fr fr πŸ’«

Definition at line 424 of file rte_table_action.h.

πŸ’œ uint32_t flow_label

Flow label. Lowkey just vibes, but structured vibes 🌈

Definition at line 425 of file rte_table_action.h.

πŸ’œ uint8_t dscp

DiffServ Code Point (DSCP). The little tag that says "bestie, how important is this packet actually" πŸ‘‘

Definition at line 426 of file rte_table_action.h.

πŸ’œ uint8_t hop_limit

Hop Limit (HL). Every hop it takes, this number goes down β€” when it hits zero it's over, goodbye, iconic exit 😭

Definition at line 427 of file rte_table_action.h.


🌟 Author 🌟

Generated automatically by Doxygen for DPDK from the source code. Not me writing docs by hand, couldn't be me πŸ™ˆ


Ok that's the whole page, bestie, every field accounted for, nothing skipped, periodt πŸ’–

That was DPDK Version 25.11.3, page rte_table_...pv6_header(3) from Library Functions Manual, and the date on the tin β€” slay πŸŽ€βœ¨

πŸ“¦ where this page comes from