rte_flow_item_port_id(3)

📦
version 25.11.3 · 9 versions
, in ubuntu resolute, ubuntu stonking

💖 rte_flow_item_port_id 💖

okay bestie, so this is a page straight out of the Library Functions Manual — it's rte_flow_item_port_id(3), and it's a lil' struct page from DPDK, kiiind of a throwback. Let's get into it 🫶

✨ NAME ✨

rte_flow_item_port_id — the struct that matches traffic by DPDK port ID, no cap 💅

✨ SYNOPSIS ✨

#include <rte_flow.h>

🌸 Data Fields 🌸

  • uint32_t id

✨ Detailed Description ✨

Deprecated 🫠 This one is literally marked deprecated, so if you're out here building something new, pls look away from it, bestie.

See also 👀

  • RTE_FLOW_ITEM_TYPE_PORT_REPRESENTOR
  • RTE_FLOW_ITEM_TYPE_REPRESENTED_PORT

So the way that RTE_FLOW_ITEM_TYPE_PORT_ID works is: it matches traffic that originates from (that's ingress) or traffic that's going to (that's egress) a given DPDK port ID. 🌈

And here's the lowkey important part — it's normally only supported if that port ID you're asking about is known by the underlying PMD, and it has to be related to the device that the flow rule is being created against. Like, the PMD has to actually recognize the vibe, yk? If it doesn't, no match for you 🙈

Definition at line 817 of file rte_flow.h. 📍

✨ Field Documentation ✨

💜 uint32_t id

DPDK port ID. That's it, that's the whole field, she's simple and she serves 🎀

Definition at line 818 of file rte_flow.h. 📍

✨ Author ✨

Generated automatically by Doxygen for DPDK, from the source code. Slay, automation 💅✨

and that's the whole page bestie!! it's giving short-but-iconic 🌟 — this was DPDK, Version 25.11.3, bringing you rte_flow_item_port_id(3). mwah, go ship something cute 🦋💖

📦 where this page comes from