nvme_init_m...ceive_create(9)

💅 NAME 💅

nvme_init_manage_export_nvms_receive_create — bestie, this is the one that initializes the passthru command for Manage Exported NVM Subsystem Receive - Create Exported NVM Subsystem ✨ (yes that's a whole mouthful, we love a descriptive queen 👑)

This page lives in the libnvme API manual — ok so now you know where you are 💖

🦋 SYNOPSIS 🦋

void nvme_init_manage_export_nvms_receive_create (struct
libnvme_passthru_cmd *cmd , bool tr , __u8 ensti , bool ra , struct
nvme_exported_nvm_subsys_create_data *data );

🎀 ARGUMENTS 🎀

• cmd — the passthru command you're gonna use, like that's the thing we're filling in 🫶
• tr — Template Required (TR), literally what it says on the tin ✨
• ensti — Exported NVM Subsystem Template Index (ENSTI), and ngl it's only used if tr is set. It indexes the Exported NVM Subsystem Template UUID List, see NVME_IDENTIFY_CNS_EXPORTED_NVM_SUBSYS_TEMPLATE_UUID_LIST 💅 (iykyk)
• ra — Restricted Access (RA): message-based transports only bestie, memory-based transports just ignore it 🙈
• data — the Create Exported NVM Subsystem data buffer, see struct nvme_exported_nvm_subsys_create_data. And here's the cute part: the assigned Exported NVM Subsystem NQN gets returned in this same buffer 🎀 lowkey convenient

🌸 DESCRIPTION 🌸

Okay so what this actually does: it initializes the passthru command buffer for the Manage Exported NVM Subsystem Receive command, with the SEL value NVME_MANAGE_EXPORT_NVMS_RECV_SEL_CREATE ✨

And the created Exported NVM Subsystem Identifier? That comes back in the CQE result, see enum nvme_export_nvms_create_cqe_dw0 💖 that's where you go looking for it, bestie, don't forget 🔥

that's the whole page, no cap — go forth and init those commands 🧚✨

💌 this lil' cutie is from the libnvme API manual, dated October 2026 — mwah, bye bestie 🫶💅