RTE_FLOW_ITEM_AGGR_AFFINITY(3)

💖 rte_flow_item_aggr_affinity 💖

okay bestie, gather round, this is a lib function page from the Library Functions Manual (section 3, for the uninitiated) and honestly? it's short, it's sweet, it's giving minimalist queen 👑

---

✨ NAME ✨

rte_flow_item_aggr_affinity — that's the whole name, that's the whole vibe, no notes 💅

---

🦋 SYNOPSIS 🦋

#include <rte_flow.h>

🌸 Data Fields 🌸

• uint8_t affinity

like... one field. one. and it's iconic for it 🎀

---

👑 Detailed Description 👑

⚠️ Warning ⚠️ EXPERIMENTAL: this structure may change without prior notice

no cap, bestie, they said it themselves — this thing is experimental, so don't you dare build your whole personality around it because it might just change on you without a heads up 😭 consider yourself warned fr fr

RTE_FLOW_ITEM_TYPE_AGGR_AFFINITY

So here's the tea ☕ when you've got multiple ports aggregated into a single DPDK port, this match is how you figure out which aggregated port is the one actually catching the packets.

Definition at line 2330 of file rte_flow.h. 📍

---

🧚 Field Documentation 🧚

🌈 uint8_t affinity

An aggregated port receiving the packets. Numbering starts from 1 — yes bestie, from one, not zero, don't come at me, that's just how it is 🙈

The number of aggregated ports is reported by rte_eth_dev_count_aggr_ports() — go check that one if you need the full headcount 🫶

Definition at line 2336 of file rte_flow.h. 📍

---

💜 Author 💜

Generated automatically by Doxygen for DPDK from the source code.

(it wasn't hand-written by a human with feelings, it was birthed by Doxygen from the source, and honestly? respect the automation 🏆)

---

aaaand that's the whole page, you ate that, you read the entire thing, main character energy only ⭐ no cap, this one was short enough to screenshot and send to the group chat 📸

mwah 💋 this little doc came straight outta DPDK, Version 25.11.3 — thanks for reading bestie, see you in the next manpage, bye bye 🦋🌸