libnvme(9)

πŸ“¦ version 3.2, in arch rolling

πŸ’… libnvme(9) β€” like, the API Manual bestie ✨

okay so listen, this one lives in the libnvme manual, section 9 β€” that's the kernel/API corner of the manual-verse, iykyk 🫢


🌸 NAME 🌸

enum nvme_export_nvms_create_mos β€” Manage Exported NVM Subsystem Receive - Create Exported NVM Subsystem - Management Operation Specific (MOS) field, message-based transports only

like yes, that name is a whole mouthful, but it's exactly what it says and we do not abbreviate the truth here πŸ’…


✨ SYNOPSIS ✨

enum nvme_export_nvms_create_mos {
    NVME_EXPORT_NVMS_CREATE_MOS_RA

};

that's the whole thing, no cap β€” one enum, one constant, zero drama πŸŽ€


πŸ¦‹ Constants πŸ¦‹

  • NVME_EXPORT_NVMS_CREATE_MOS_RA β€” Restricted Access (RA) πŸ‘‘

that's the entire roster. one icon, one job, and it ate πŸ”₯


🧚 heads up bestie: the NAME line is really specific about it β€” this is the Management Operation Specific (MOS) field, and it's for message-based transports only. not all transports, just the message-based ones. don't come for me, that's literally what it says πŸ™ˆ

and that's the vibe check, we're done! πŸ’– this little page came from the API Manual and is dated October 2026, and the header/footer both rep libnvme(9) and enum nvme_export_nvms_create_mos β€” slay, mwah πŸ˜˜πŸ’œ

πŸ“¦ where this page comes from