rte_flow_action(3)

πŸ’– rte_flow_action πŸ’–

okay bestie, so rte_flow_action(3) is literally one of those Library Functions Manual pages, and we're about to make it make sense. no cap, this one's short but it's important. 🫢


πŸŽ€ NAME πŸŽ€

rte_flow_action β€” that's the whole name, that's the girl. ✨


🌸 SYNOPSIS 🌸

include her, bestie:

#include <rte_flow.h>

πŸ¦‹ Data Fields

here's the tea, the two fields you're gonna be looking at:

  • enum rte_flow_action_type type
  • const void * conf

πŸ’… DETAILED DESCRIPTION πŸ’…

okay so this is the definition of a single action. one action. just her. πŸŽ€

an entire list of actions? it gets terminated by an END action. that's the vibe check, that's how you know the list is done. πŸ’€

and here's the lowkey crucial part: for simple actions that don't have a configuration object, conf stays NULL. no config, no pointer, no problem. ✨

fr fr, this definition lives at line 4291 of the file rte_flow.h. not me having the receipts saved. 😭


πŸ‘‘ FIELD DOCUMENTATION πŸ‘‘

πŸ’œ enum rte_flow_action_type type

this bad boy is the action type. that's it, that's her whole job. πŸ¦‹

she's defined at line 4292 of the file rte_flow.h.

πŸ“ const void* conf

and this one is a pointer to the action configuration object. the actual deets of what the action does live wherever she's pointing. ✨

she's sitting pretty at line 4293 of the file rte_flow.h.


🌈 AUTHOR 🌈

generated automatically by Doxygen for DPDK, straight from the source code. not a human typing this out at 3am β€” it's the machine doing it, and honestly? she ate. πŸ’…

and that's a wrap on rte_flow_action(3) β€” pinky promise you got it. this whole thing is DPDK, Version 25.11.3, which is basically the group-chat footer of manpages. periodt. πŸ’–πŸŒŸπŸŽ€

πŸ“¦ where this page comes from