libnvme(9)

🦋 libnvme(9) — the API Manual, bestie edition 🦋

Okay so bestie, we're deep in the libnvme API manual today and honestly? This one's a little gem. ✨

💖 NAME 💖

enum nvme_mi_message_type — the NVMe-MI message type field. That's it, that's the whole vibe check. 💅

---

🌸 SYNOPSIS 🌸

Here's the whole enum, laid out exactly like this, no cap:

enum nvme_mi_message_type {
    NVME_MI_MT_CONTROL ,
    NVME_MI_MT_MI ,
    NVME_MI_MT_ADMIN ,
    NVME_MI_MT_PCIE ,
    NVME_MI_MT_AE

};

Five constants, all iconic, all doing their own thing. 🫶

---

⭐ Constants ⭐

These are the actual values, and yes every single one matters — not me skipping a single one, we're doing this properly:

• NVME_MI_MT_CONTROL — the NVME-MI Control Primitive. Very official. Very "I'm the one who knocks". 👑
• NVME_MI_MT_MI — an NVMe-MI command. It's giving main character energy, obviously. 🔥
• NVME_MI_MT_ADMIN — an NVMe Admin command. The responsible one of the group. 🎀
• NVME_MI_MT_PCIE — a PCIe command. Hardware girlies rise. 🦋
• NVME_MI_MT_AE — an Asynchronous Event. It literally shows up whenever it wants, no warning, so rude, so slay. 😭

---

💜 Description 💜

So where does this thing actually live? It's used as byte 1 of both the request and response messages — that's the NMIMT bits of the NMP byte. Ngl kind of a specific spot but okay, we respect it. ⭐

🚨 Real talk though: do not confuse this with the MCTP message type in byte 0. Byte 0 is a whole different girlie. Keep them separate or you will be sad. 💀

---

✨ Sign-off ✨

That's the page, bestie! This little beauty is dated October 2026, it's filed under enum nvme_mi_message_type, and it's part of libnvme(9). Go forth and encode your bytes correctly. 💅🌈🍓