rte_eth_dc...ue_mapping(3)

✨ NAME ✨

rte_eth_dcb_tc_queue_mapping — the struct that hands you the tea on how queues and TCs (traffic classes) are mapped on both the Tx and the Rx paths 🦋

(also hey bestie, this page lives in the Library Functions Manual, and its name up top is rte_eth_dc...ue_mapping(3) — yes the name is literally truncated with dots, that's just how the header prints it, we don't make the rules 💅)

---

💖 SYNOPSIS 💖

#include <rte_ethdev.h>

🎀 Data Fields 🎀

struct {
} tc_rxq[RTE_ETH_MAX_VMDQ_POOL][RTE_ETH_DCB_NUM_TCS]
struct {
} tc_txq[RTE_ETH_MAX_VMDQ_POOL][RTE_ETH_DCB_NUM_TCS]

okay so yes, those are anonymous structs, that's not me being lazy, that is genuinely what's there. periodt.

---

🌸 Detailed Description 🌸

So this struct exists for exactly one iconic purpose: to get you the info about queue and TC mapping on both the Tx and the Rx paths. That's it. That's the whole job. And it ate. 👑

Definition at line 2006 of file rte_ethdev.h.

---

🧚 Field Documentation 🧚

⭐ struct { ... } tc_rxq[RTE_ETH_MAX_VMDQ_POOL][RTE_ETH_DCB_NUM_TCS]

Rx queues assigned to tc per Pool. 💖

Two dims, bestie: RTE_ETH_MAX_VMDQ_POOL across, RTE_ETH_DCB_NUM_TCS down, and inside each cell is a lil anonymous struct. It's giving "nested array energy" and we're obsessed.

🌈 struct { ... } tc_txq[RTE_ETH_MAX_VMDQ_POOL][RTE_ETH_DCB_NUM_TCS]

Rx queues assigned to tc per Pool.

lowkey yes, the doc literally says Rx on the tc_txq line too 🙈 I'm not paraphrasing it away, I'm reporting it exactly as the page has it. If that's a typo, that's a docs typo, not a me typo, and the actual field name is still tc_txq and the dims are still RTE_ETH_MAX_VMDQ_POOL and RTE_ETH_DCB_NUM_TCS. no cap.

---

💜 Author 💜

Generated automatically by Doxygen for DPDK from the source code. not a human main character, just a very hardworking generator 🫶

---

and that's the whole page, bestie — DPDK, Version 25.11.3 🌈 no date on this footer fr fr, just the version, so that's the vibe check and we're logging off 💅✨🎀