rte_flow_a...plate_attr(3)

πŸ’– rte_flow_actions_template_attr πŸ’–

okay bestie, so this page lives in section 3 of the manual β€” the Library Functions Manual β€” and it's literally called rte_flow_actions_template_attr. it's a struct, it's tiny, it's kinda iconic, and we're gonna go through it together, no skip, fr fr. πŸŽ€


✨ NAME ✨

rte_flow_actions_template_attr β€” the attributes struct for a flow actions template. that's it, that's the name, slay.


🌸 SYNOPSIS 🌸

you pull it in like this:

#include <rte_flow.h>

πŸ¦‹ Data Fields

  • uint32_t ingress:1
  • uint32_t egress:1
  • uint32_t transfer:1

three little one-bit flags, sitting there, minding their business, being the entire personality of this struct. πŸ’…


πŸ‘‘ Detailed Description πŸ‘‘

Warning β€” EXPERIMENTAL: this API may change without prior notice. 😭 so like, don't get too attached, okay? it's giving "situationship with the ABI".

Flow actions template attributes. yeah. that's the whole description. it's a struct that holds the attributes for a flow actions template β€” the ingress/egress/transfer vibes we're about to get into. 🫢

Definition at line 5785 of file rte_flow.h.


πŸ’œ Field Documentation πŸ’œ

uint32_t ingress

Flow direction for the actions template. At least one direction must be specified β€” so like, you cannot leave all three at zero, bestie, that's not a mood that works here. πŸ™ˆ

Action valid for rules applied to ingress traffic. i.e. stuff coming in. inbound. the main character arriving at the party. ✨

Definition at line 5791 of file rte_flow.h.</puge>

uint32_t egress

Action valid for rules applied to egress traffic. stuff heading out. departing. waving bye at the door. πŸ¦‹

Definition at line 5793 of file rte_flow.h.

uint32_t transfer

Action valid for rules applied to transfer traffic. transfer traffic has its own whole lane and it's a whole vibe, iykyk. 🌈

Definition at line 5795 of file rte_flow.h.


πŸŽ€ Author πŸŽ€

Generated automatically by Doxygen for DPDK from the source code. so nobody wrote this with love, a robot did, and honestly? still ate. 😌


πŸ’€ rember bestie: at least one of ingress, egress or transfer has to be set. zero directions = invalid. that's the whole rule, don't fight it.

and that's the page!! short king of a manpage, three fields, one warning, done. πŸ’–

⭐ sign-off time: this was the DPDK version 25.11.3 rendering of rte_flow_a...plate_attr(3) β€” go set some flow directions, ily, bye!! 🫢🌸

πŸ“¦ where this page comes from