libnvme(9)

libnvme(9) 💅

okay so bestie, welcome to the libnvme(9) API manual — yes that's the manual name, and yes it's giving "I read kernel docs for fun" and honestly? iconic. sit down, hydrate, let's talk about one very specific enum. 🫶

---

✨ NAME ✨

enum nvme_subsys_type — the type of the NVM subsystem. literally just: what kind of subsystem are we talking about, bestie. that's the whole vibe check.

---

🌸 SYNOPSIS 🌸

enum nvme_subsys_type {
    NVME_NQN_DISC ,
    NVME_NQN_NVME ,
    NVME_NQN_CURR

};

that's it. three constants, zero drama. copy it exactly, don't @ me. 💅

---

🎀 Constants 🎀

the main characters, one by one. 👑

• NVME_NQN_DISC — Discovery type target subsystem. this one describes a referral to another Discovery Service, which is itself made up of Discovery controllers that hand out extra discovery records. and listen: multiple Referral entries may be reported for each Discovery Service — that happens if that Discovery Service has multiple NVM subsystem ports, or if it supports multiple protocols. so yeah, you might see it more than once. not a glitch, that's just how she is. 🦋
• NVME_NQN_NVME — NVME type target subsystem. this is the one that describes an NVM subsystem whose controllers may have attached namespaces (i.e. an NVM subsystem that is not composed of Discovery controllers — very "I have actual work to do" energy). multiple NVM Subsystem entries may be reported for each NVM subsystem if that NVM subsystem has multiple NVM subsystem ports. so again: multiples are legit, bestie. 🔥
• NVME_NQN_CURR — Current Discovery type target subsystem. this describes this Discovery subsystem — like, the Discovery Service that contains the controller that's processing the Get Log Page command. multiple Current Discovery Subsystem entries may be reported for this Discovery subsystem if the current Discovery subsystem has multiple NVM subsystem ports. it's giving "look in the mirror" but in a spec-compliant way. 🪞✨

lowkey the pattern here is: multiple entries = multiple ports. that's the whole lore. iykyk. 💀

---

and that's the page, bestie — no cap, you now know your subsystem types. 🧚

sign-off era: this was enum nvme_subsys_type from the libnvme(9) API Manual, dated October 2026 — and just so we're clear, that's the source/version and date, not me being mysterious. mwah 💜🎀