rte_flow_action_prog(3)

💖 NAME 💖

rte_flow_action_prog — bestie, it's a struct, and it's the whole personality of the PROG flow action ✨

---

✨ SYNOPSIS ✨

#include <rte_flow.h>

🎀 Data Fields

• const char * name
• uint32_t args_num
• const struct rte_flow_action_prog_argument * args

---

🌸 DETAILED DESCRIPTION 🌸

⚠️ Warning — EXPERIMENTAL: this structure may change without prior notice. Not me telling you your fave could get rewritten overnight 😭

RTE_FLOW_ACTION_TYPE_PROG

Program action configuration parameters. That's the whole job, and it does it gorgeously 💅

Every action can have zero or more arguments — yes, zero is a valid number of args, we love a flexible queen 🫶. But the moment args_num is non-zero, the args parameter must point to a valid array of args_num elements. No cap, it has to actually be valid or you're in your flop era 💀

See also 👀

• RTE_FLOW_ACTION_TYPE_PROG

Definition at line 4233 of file rte_flow.h. 👑

---

🦋 FIELD DOCUMENTATION 🦋

Time for the field-by-field vibe check, one icon at a time 🌈

const char* name

Action name. That's it, that's the field — a whole legend with a first name basis situation 💜

Definition at line 4235 of file rte_flow.h.

uint32_t args_num

Number of action arguments. Literally just counting your little guys 🔢✨

Definition at line 4237 of file rte_flow.h.

const struct rte_flow_action_prog_argument* args

Action arguments array. The squad. The ensemble cast. Every element matters 🍓

Definition at line 4239 of file rte_flow.h.

---

👑 AUTHOR 👑

Generated automatically by Doxygen for DPDK from the source code. So no human author to stan, the robot did it and honestly? It ate 🤖💅

---

That's the page bestie — brought to you by the DPDK squad, Version 25.11.3, and yeah the date situation is whatever the header said, but the version is right there and it's iconic. Slay, compile something, and remember: zero args is valid, a lying args_num is not 🌟🧚💖