rte_flow_action_port_id(3)

🌸 NAME 🌸

rte_flow_action_port_id — that’s the name, bestie. The manual page is rte_flow_action_port_id(3) from the Library Functions Manual, and this is where we keep all the details. 🦋

✨ SYNOPSIS ✨

First, include the header like this, no skipping:

#include <rte_flow.h>

🎀 Data Fields 🎀

Here are the data fields, exactly as they show up:

• uint32_t original:1
• uint32_t reserved:31
• uint32_t id

💖 Detailed Description 💖

Okay so the major tea: Deprecated. That’s the official status, bestie — it’s giving legacy, so keep that in mind. 💀

👀 See also 👀

• RTE_FLOW_ACTION_TYPE_PORT_REPRESENTOR
• RTE_FLOW_ACTION_TYPE_REPRESENTED_PORT

Also in the mix: RTE_FLOW_ACTION_TYPE_PORT_ID.

rte_flow_action_port_id directs matching traffic to a given DPDK port ID. That’s the main character move. 🎯

🌟 See also 🌟

• RTE_FLOW_ITEM_TYPE_PORT_ID

Definition at line 3552 of file rte_flow.h.

🧚 Field Documentation 🧚

💅 uint32_t original 💅

If possible, use the original DPDK port ID. ✨

Definition at line 3553 of file rte_flow.h.

🚫 uint32_t reserved 🚫

Reserved — and it must be zero, no cap. Like, do not put anything else there. 💀

Definition at line 3554 of file rte_flow.h.

👑 uint32_t id 👑

The DPDK port ID. Periodt. 💖

Definition at line 3555 of file rte_flow.h.

👑 AUTHOR 👑

Generated automatically by Doxygen for DPDK from the source code. Yes, the robots did this one — iconic. 🤖✨

---

Okay that’s the whole page, bestie! This one comes from DPDK, Version 26.03.0, for rte_flow_action_port_id(3) — and the footer has no date listed, so we’re not inventing one. Bye, slay your port IDs! 💖✨🦋