STRUCT NITROX_DEVICE(9)

💖 struct nitrox_device(9) 💖

okay bestie, so this is the Kernel API Manual page for struct nitrox_device — the NITROX Device Information struct ✨. if you've ever wondered "what even is a nitrox device, and what's living inside it," this is literally the whole vibe check. scroll with me 🫶

---

✨ NAME ✨

struct nitrox_device — NITROX Device Information. that's it, that's the whole thing, she's a struct and she's iconic 💅

---

🌸 SYNOPSIS 🌸

here's the literal anatomy of her, no cap, copy-pasted straight from the source so you don't get any funny ideas:

struct nitrox_device {
    struct list_head list;
    u8 __iomem *bar_addr;
    struct pci_dev *pdev;
    atomic_t state;
    unsigned long flags;
    unsigned long timeout;
    refcount_t refcnt;
    u8 idx;
    int node;
    u16 qlen;
    u16 nr_queues;
    enum vf_mode mode;
    struct dma_pool *ctx_pool;
    struct nitrox_cmdq *pkt_inq;
    struct nitrox_cmdq *aqmq[MAX_DEV_QUEUES];
    struct nitrox_q_vector *qvec;
    struct nitrox_iov iov;
    int num_vecs;
    struct nitrox_stats stats;
    struct nitrox_hw hw;
  #if IS_ENABLED(CONFIG_DEBUG_FS);
    struct dentry *debugfs_dir;
  #endif;
};

like, look at all those fields. main character energy fr 🔥

---

🎀 Members 🎀

this is the part where we meet every single field one by one, like a little meet-and-greet but for struct members 🧚

• list — pointer to the linked list of devices. she's connected, she has friends 💫
• bar_addr — the iomap address. that's where the memory-mapped action happens ✨
• pdev — PCI device information, so you know which physical device we're talking about 🦋
• state — NITROX device state. how's she doing? this tells you 💜
• flags — flags to indicate device the features. yes, that's the wording, love that for us 💅
• timeout — Request timeout, measured in jiffies. tick tock bestie ⏰
• refcnt — Device usage count. how many people are holding onto her rn 🙈
• idx — device index, in the range 0..N 🔢
• node — the NUMA node id she's attached to. she knows her local memory 🌸
• qlen — Command queue length 📏
• nr_queues — Number of command queues. the more the merrier honestly 👑
• mode — Device mode, PF/VF — she's either physical or virtual, pick a lane 💫
• ctx_pool — DMA pool for crypto context. spa day for your crypto context 🛁
• pkt_inq — Packet input rings 💍
• aqmq — AQM command queues 🗣️
• qvec — MSI-X queue vectors information 📬
• iov — SR-IOV informatin (yes, that's literally how it's spelled in the source — don't come for me, I don't make the typos 💀)
• num_vecs — number of MSI-X vectors 🔢
• stats — request statistics. the receipts 📊
• hw — hardware information 🛠️
• debugfs_dir — the debugfs directory. peek behind the curtain bestie 👀

---

🌈 SEE ALSO 🌈

go read these next, they're giving the same energy:

• Kernel file ./drivers/crypto/cavium/nitrox/nitrox_dev.h struct
• nitrox_cmdq(9)
• struct nitrox_hw(9)
• struct nitrox_iov(9)
• nitrox_read_csr(9)
• nitrox_write_csr(9)

---

okay that's the whole page, you ate that bestie 🍓 and for the cute sign-off: this one lives at ./drivers/crypto/cavium/nitrox, it's dated October 2026, and it goes by struct nitrox_device(9) 🦋💖 mwah, bye!! ⭐