RTE_SWX_CTL_ACTION_ARG_INFO(3)

✨ NAME ✨

rte_swx_ctl_action_arg_info — bestie, it's a struct. A whole little struct living in the Library Functions Manual, section 3, and it's the moment you learn what an action argument actually is 💅

---

🦋 SYNOPSIS 🦋

#include <rte_swx_ctl.h>

🌸 Data Fields 🌸

char name[RTE_SWX_CTL_NAME_SIZE]
uint32_t n_bits
int is_network_byte_order

---

💖 DESCRIPTION 💖

Detailed Description

Okay so Action argument info. That's the whole vibe. It's the struct that holds the deets on one single action argument, no more no less 🫶

It's defined at line 182 of the file rte_swx_ctl.h. Iconic. Put that in your notes.

---

🎀 FIELD DOCUMENTATION 🎀

💜 char name[RTE_SWX_CTL_NAME_SIZE]

The action argument name. That's it, that's the field. It lives at line 184 of rte_swx_ctl.h.

---

⭐ uint32_t n_bits

The size of the action argument, and how is it measured? In bits, obviously ✨ Not bytes, not vibes — bits. Defined at line 187 of rte_swx_ctl.h.

---

👑 int is_network_byte_order

Ooh this one's the main character. So listen:

• Non-zero (which means true) when this action argument must be stored in the table in network byte order (NBO) 🌐
• Zero, meaning false, when it must be stored in host byte order (HBO) 🏠

That's the whole story: one int, two possible byte-order destinies. Sit with that. Defined at line 193 of rte_swx_ctl.h.

---

🫶 AUTHOR 🫶

Generated automatically by Doxygen for DPDK from the source code. Not a human girlie typing this out by hand, a robot did it, and honestly? It ate 💀

---

no cap, everything above is straight from the header — rte_swx_ctl.h is the source of truth, always check it, iykyk 🦋

---

k bye bestie, this was DPDK Version 25.11.3, page rte_swx_ct...on_arg_info(3), coming at you from the Library Functions Manual 💖 mwah 🎀