NVME_INIT_MANAGE_EXPORT_NVMS_SEND_DELETE-LIBNVME3(2)

πŸ“¦ version 3.2, in arch rolling

πŸ’… nvme_init_manage_export_nvms_send_delete β€” the libnvme API manual, bestie edition

okay so picture this: you're deep in libnvme land, the land of the libnvme API manual, and you need to tell a controller "hey girl, delete this exported NVM subsystem for me." That's literally this function. Her full government name is nvme_init_manage_export_nvms_send_delete and she's the one who sets up the passthru command for you. No cap, she's just the setup girl β€” she doesn't send it, she initializes it. Big difference, iykyk. ✨


🌸 SYNOPSIS 🌸

void nvme_init_manage_export_nvms_send_delete (struct
     libnvme_passthru_cmd *cmd , bool esubidv , __u16 esubid , struct
     nvme_exported_nvm_subsys_nqn_data *data );

like, she returns void β€” nothing comes back, she just does the thing to cmd and dips. 🫢


πŸŽ€ ARGUMENTS πŸŽ€

  • cmd β€” the passthru command you're gonna use. this is the blank canvas bestie, she fills it in for you. πŸ–ŒοΈ
  • esubidv β€” the Exported NVM Subsystem Identifier Valid flag, aka ESUBIDV. if it's set, then esubid is the one that identifies which Exported NVM Subsystem to delete. if it's not set, then the subsystem gets identified by the SUBNQN in data instead. it's giving "pick a lane" energy and honestly? valid. πŸ’…
  • esubid β€” the Exported NVM Subsystem Identifier, aka ESUBID. this one only matters if esubidv is set. no esubidv? then she's just standing there, unused. πŸ™ˆ
  • data β€” the Exported NVM Subsystem NQN data buffer. peep struct nvme_exported_nvm_subsys_nqn_data for the deets. and listen β€” if esubidv is set, data gets ignored entirely. not even a little bit used. πŸ’€

✨ DESCRIPTION ✨

so what does she actually do? she initializes the passthru command buffer for the Manage Exported NVM Subsystem Send command, with the SEL value set to NVME_MANAGE_EXPORT_NVMS_SEND_SEL_DELETE. that's the whole vibe. she's the "delete" flavor of that Send command, prepped and ready for you to fire off. πŸ”₯

heads up bestie: she initializes the buffer, she doesn't submit the command. that part's on you. periodt. πŸ‘‘


and that's the whole page, bestie β€” no SEE ALSO, no return value drama, just a clean little setup function doing her one job beautifully. this icon of a function comes to you from the libnvme API manual, dated October 2026, and her footer energy is literally: nvme_init_manage_export_nvms_send_delete(9). slay, go delete some exported NVM subsystems responsibly. πŸ¦‹πŸ’œ

πŸ“¦ where this page comes from