rte_pci_id(3)

💖 NAME 💖

okay bestie, meet rte_pci_id — a whole lil struct that lives in the DPDK library functions manual (it's a 3 page, iykyk).

---

🎀 SYNOPSIS 🎀

First things first, you gotta pull it in:

#include <rte_pci.h>

✨ Data Fields ✨

here's the whole squad of fields, no cap, all of them:

• uint32_t class_id
• uint16_t vendor_id
• uint16_t device_id
• uint16_t subsystem_vendor_id
• uint16_t subsystem_device_id

---

🦋 Detailed Description 🦋

so this struct is literally an ID for a PCI driver. the way it works is: each driver hands over a whole table of these IDs, one for every single device it supports. it's giving matchmaking, but for hardware 💅

Definition at line 170 of file rte_pci.h.

---

🌸 Field Documentation 🌸

💜 uint32_t class_id

the Class ID — or, if you're feeling chaotic and wanna match literally anything, RTE_CLASS_ANY_ID.

Definition at line 171 of file rte_pci.h.

💜 uint16_t vendor_id

the Vendor ID — or RTE_PCI_ANY_ID if you're in your "any vendor is fine, I'm not picky" era.

Definition at line 172 of file rte_pci.h.

💜 uint16_t device_id

the Device ID — or, you guessed it, RTE_PCI_ANY_ID.

Definition at line 173 of file rte_pci.h.

💜 uint16_t subsystem_vendor_id

the Subsystem vendor ID — or RTE_PCI_ANY_ID, same energy as always.

Definition at line 174 of file rte_pci.h.

💜 uint16_t subsystem_device_id

the Subsystem device ID — and yes, RTE_PCI_ANY_ID again, she's consistent periodt.

Definition at line 175 of file rte_pci.h.

---

👑 Author 👑

not a human bestie — this was generated automatically by Doxygen for DPDK, straight from the source code. iconic honestly.

---

okay that's the whole page!! 🫶 huge thanks to DPDK for this one — this manual page is from DPDK Version 25.11.3, and it's filed under the rte_pci_id(3) page in the Library Functions Manual. slay, go compile something, mwah 💅✨🎀