libnvme(9)

💅 libnvme(9) — the libnvme API manual, bestie edition 🦋

Okay so this page is literally all about one little struct from the libnvme API manual, and we're gonna stan it properly. Let's go ✨

---

🌸 NAME 🌸

struct nvme_mi_control_req — the Control Primitive request, no cap 🎀

Like, that's its whole thing. That's the job. It's the request side of a Control Primitive, and it's giving main character energy in struct form 👑

---

⭐ SYNOPSIS ⭐

Here's the shape of it, exactly as it lives in the header — copy it faithful, don't touch a single character 🫶

struct nvme_mi_control_req {
    struct nvme_mi_msg_hdr hdr;
    __u8 opcode;
    __u8 tag;
    __le16 cpsp;
 };

That's the whole vibe. Four little members, one big mood. 🧚

---

💖 Members 💖

🍓 hdr

Generic MI message header — that's it, that's the note. It's the generic header for the MI message, the boring-but-essential scaffolding holding everything up. Lowkey the backbone of the operation 💀

🦋 opcode

Control Primitive Opcodes — and it's using enum nvme_mi_control_opcode, iykyk. So this field is where the actual opcode goes, picked from that enum. Not me being obsessed with a __u8 but here we are 😭

🌈 tag

A flag — an opaque value that gets passed from the request to the response. Opaque means you don't peek inside it, you just carry it along like a lil emotional support value 🎀 The request hands it over, the response receives it. Periodt.

✨ cpsp

Control Primitive Specific Parameter. Yes, that's really the name, and yes, it's a __le16, and yes, it's specific to whatever Control Primitive you're doing. It's giving "details inside" energy 💅

---

Fr fr reminder bestie: cpsp is little-endian (__le16) and tag is opaque — don't go reading meaning into it, just pass it through 🙈

---

👑 cute sign-off 👑

This lil page is struct nvme_mi_control_req from libnvme(9), dated October 2026 — so like, future girl summer 🌸 Go forth and slay your Control Primitive requests, bestie. Mwah 💜🔥