NVME_INIT_MANAGE_EXPORT_NVMS_RECEIVE_LIST_SUBSYSTEMS-LIBNVME3(2)
π nvme_init_manage_export_nvms_receive_list_subsystems(9) β the libnvme API manual, bestie edition π
okay so this is a page straight out of the libnvme API manual, and it's about one very specific little function with the longest name in the group chat: nvme_init_manage_export_nvms_receive_list_subsystems. yes, that's really it, no I'm not kidding, and yes you will be typing it a lot. it's giving "my parents named me after the whole family tree" energy π but honestly? iconic. let's get into it β¨
πΈ NAME πΈ
nvme_init_manage_export_nvms_receive_list_subsystems β Initialize passthru command for Manage Exported NVM Subsystem Receive - List Exported NVM Subsystems π¦
like, that's the whole job. it sets up your passthru command so it's ready to go ask for the list of exported NVM subsystems. no cap, that's it π
β¨ SYNOPSIS β¨
void nvme_init_manage_export_nvms_receive_list_subsystems (struct
libnvme_passthru_cmd *cmd , __u16 esubid , struct
nvme_exported_nvm_subsys_list *list , __u32 len );
notice the void bestie β nothing comes back, it just does its thing and you move on π
π«Ά ARGUMENTS π«Ά
cmdβ the passthru command to use. this is your blank canvas, your main character struct, and this function is about to fill it in πesubidβ Return Exported NVM Subsystems with an Exported NVM Subsystem Identifier greater than or equal to this value. so it's a "start from here" marker, not a filter that only matches one thing β greater than or equal to, fr fr π₯listβ User address to store the Exported NVM Subsystems List data structure, seestruct nvme_exported_nvm_subsys_list. you're handing over where the results should land, so make sure it's a real place you own πlenβ the allocated length oflist. heads up: this is how big your buffer actually is, so like... don't lie about it π
π DESCRIPTION π
Initializes the passthru command buffer for the Manage Exported NVM Subsystem Receive command with SEL value NVME_MANAGE_EXPORT_NVMS_RECV_SEL_LIST_SUBSYSTEMS.
that's the whole vibe. it preps the command buffer, pins the SEL to NVME_MANAGE_EXPORT_NVMS_RECV_SEL_LIST_SUBSYSTEMS, and hands it back to you ready for the actual passthru. you bring the command struct, it brings the setup. team effort π§π
this is a void function, so don't go looking for a return value to check β there isn't one, bestie. set your stuff up right before you call it π
and that's the page!! π written by the libnvme crew, October 2026, from the libnvme API manual, page nvme_init_manage_export_nvms_receive_list_subsystems(9) β mwah, go slay your passthru commands πβ¨π
π¦ where this page comes from
- arch rolling: nvme-cli 3.2-1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms