libnvme(2)

πŸ’– libnvme(2) β€” API Manual πŸ’–

okay bestie, welcome to the <enum> part of the libnvme API manual πŸ’… if you're here it's because you're poking at namespace identifier descriptor types, and honestly? iconic behavior. let's get into it.


✨ NAME ✨

enum nvme_ns_id_desc_nidt β€” the known namespace identifier types πŸ‘‘

🌸 SYNOPSIS 🌸

enum nvme_ns_id_desc_nidt {
    NVME_NIDT_EUI64 ,
    NVME_NIDT_NGUID ,
    NVME_NIDT_UUID ,
    NVME_NIDT_CSI

};

so yeah, that's the whole enum, that's the vibe check right there πŸ¦‹

πŸŽ€ Constants πŸŽ€

each one of these lil guys is a possible value for the identifier type, and here's exactly what each means:

  • NVME_NIDT_EUI64 β€” IEEE Extended Unique Identifier, and the NID field holds a copy of the EUI64 field in the struct nvme_id_ns.eui64. she's literally just the EUI64 with a pass-through, no cap πŸ’«
  • NVME_NIDT_NGUID β€” Namespace Globally Unique Identifier, and the NID field holds a copy of the NGUID field in struct nvme_id_ns.nguid. same energy, different field 🫢
  • NVME_NIDT_UUID β€” the NID field holds a 128-bit Universally Unique Identifier (UUID) as specified in RFC 4122. very main character of her honestly 🌈
  • NVME_NIDT_CSI β€” the NID field holds the command set identifier. the way that she just tells you the command set... obsessed πŸ”₯

πŸ¦‹ SEE ALSO πŸ¦‹

hmm, there's genuinely nothing else listed in this one bestie, so the see-also moment is just us, vibing πŸ§šπŸ’œ


fr fr, that's the whole page. nothing left unread, every constant accounted for. slay. ✨

and that's a wrap, bestie! this was enum nvme_ns_id_desc_nidt from the libnvme(2) API Manual, dated July 2026. go forth and identify your namespaces with confidence πŸ’…πŸ’–πŸŽ€

πŸ“¦ where this page comes from