NVME_INIT_MANAGE_EXPORT_NVMS_RECEIVE_LIST_NAMESPACES-LIBNVME3(2)

💅 nvme_init_manage_export_nvms_receive_list_namespaces — NAME

okay so bestie, this one is nvme_init_manage_export_nvms_receive_list_namespaces from the libnvme API manual (section 9, iykyk). its whole personality is: initialize the passthru command for Manage Exported NVM Subsystem Receive — List Exported Namespaces. that's it, that's the vibe. it's the setup girlie, not the one doing the actual receiving ✨

---

🦋 SYNOPSIS

void nvme_init_manage_export_nvms_receive_list_namespaces (struct
libnvme_passthru_cmd *cmd , __u32 nsid , struct nvme_exported_ns_list
*list , __u32 len );

no cap, it returns void — she sets things up and dips, no return value, no drama 💅

---

🎀 ARGUMENTS

• cmd — the passthru command you're gonna use. she initializes this one, bestie 🫶
• nsid — this is where it gets cute: you're asking for the Exported Namespaces associated with this Exported NVM Subsystem, and only the ones whose Exported Namespace Identifier is greater than this value. so it's like "give me everything after this point", lowkey a cursor 🌸
• list — the user address where the Exported Namespace List data structure goes. it's struct nvme_exported_ns_list, go look at it, iconic struct fr fr 📋
• len — the allocated length of list. how much room you gave her 💖

---

🌈 DESCRIPTION

so what she actually does: she initializes the passthru command buffer for the Manage Exported NVM Subsystem Receive command, with the SEL value set to NVME_MANAGE_EXPORT_NVMS_RECV_SEL_LIST_NAMESPACES. that's the whole job, and honestly? she ate 👑

like literally all the magic is in that SEL value — put it in, buffer is ready, go send your command 🚀

---

⚠️ reminder bestie: len has to match the allocated length of list, and list has to be a real user address you own. don't be out here pointing at vibes 💀

---

and that's the page!! 🧚 from the libnvme API manual, section 9 — dated October 2026 in the footer. mwah, go init some commands 💜