rte_pipeline_params(3)

🌸 NAME 🌸

rte_pipeline_params — bestie, this is the struct you fill out when you're setting up a pipeline, and it's literally the whole vibe check for that creation 💅

---

✨ SYNOPSIS ✨

#include <rte_pipeline.h>

💖 Data Fields 💖

• const char * name
• int socket_id
• uint32_t offset_port_id

---

🦋 DESCRIPTION 🦋

Okay so this struct is the parameters for pipeline creation 🎀 like, it's what you hand over when you want a pipeline to exist and you're telling the library where it should live and what to call itself.

Fr fr, this is Definition at line 71 of file rte_pipeline.h — go touch grass in the header if you want to see it in the wild 🫶

---

🧚 FIELD DOCUMENTATION 🧚

⭐ const char* name

Pipeline name ✨ That's it, that's the field. Give the girl a name 👑

Definition at line 73 of file rte_pipeline.h.

🌈 int socket_id

The CPU socket ID where memory for the pipeline and its elements (ports and tables) should be allocated 🧠✨ So yes, not just the pipeline itself — the ports and the tables get parked on that socket too, iykyk.

Definition at line 77 of file rte_pipeline.h.

🔥 uint32_t offset_port_id

The offset within packet meta-data to port_id, and this is the one to be used by the action "Send packet to output port read from packet meta-data" 🎯

⚠️ Warning bestie: it has to be 4-byte aligned. No cap. Misalign it and you're gonna have a bad time 😭

Definition at line 82 of file rte_pipeline.h.

---

👑 AUTHOR 👑

Generated automatically by Doxygen for DPDK from the source code 🫡 so nobody hand-wrote this and nobody's taking credit, that's just how the docs pipeline rolls.

---

And that's the whole page, bestie 💜 Big sign-off energy: this bad boy is from the DPDK docs, Version 26.03.0, and the footer's manual name is rte_pipeline_params(3) — no date on this one, so don't come for me 🙈 💅