libnvme(2)

💖 NAME 💖

ok so bestie, welcome to libnvme — this page is all about struct nvme_mi_mi_req_hdr, aka the MI request message header 🫶 she's a struct, she's iconic, she's how you say "hey NVMe-MI, I have a request" ✨

---

🌸 SYNOPSIS 🌸

like, here's the whole vibe, literally verbatim:

struct nvme_mi_mi_req_hdr {
    struct nvme_mi_msg_hdr hdr;
    __u8 opcode;
    __u8 rsvd0[3];
    __le32 cdw0, cdw1;
 };

no cap, that's it. four-ish members and she's done 💅

---

🎀 Members 🎀

okay so let's go member by member, main character energy only:

• hdr — it's the generic MI message header, the universal intro every MI message has to make 🦋
• opcode — the opcode (aka OPC), which tells everyone which specific MI command this is. it's giving "hi, this is what I want" 👑
• rsvd0 — reserved bytes. not for you. hands off, bestie 🙈 that's reserved space, periodt.
• cdw0 — Management Request Doubleword 0. the usage is command-specific, so don't come at it expecting one fixed meaning, iykyk.
• cdw1 — Management Request Doubleword 1. again, command-specific usage — it means whatever the command says it means 💜

---

🌈 Description 🌈

so basically? this is the wire format for MI request message headers, defined in section 5 of NVMe-MI ⭐ that's the whole lore. this is what goes on the wire when you're sending an MI request, and the spec (section 5, NVMe-MI) is where all the receipts live 📜

no invented behaviour here, bestie — if you wanna know what a specific opcode or cdw0/cdw1 actually does for your command, that's a job for the spec, not for me 💀

---

and that's the page!! ✨ slay 💖

this was struct nvme_mi_mi_req_hdr from the API Manual for libnvme, section 2. date stamp on this one: July 2026 🌸 go forth and send MI requests responsibly, mwah 🫶🎀