nvme_init_m...rt_nvms_send(9)
πΈ nvme_init_manage_export_nvms_send πΈ
okay bestie, welcome to the nvme_init_m...rt_nvms_send(9) page from the libnvme API manual β yes, the title is a little elided, but the function is nvme_init_manage_export_nvms_send, and she is here to set up a passthru command. π
β¨
π NAME π
nvme_init_manage_export_nvms_send β Initialize passthru command for Manage Exported NVM Subsystem Send. That's the whole assignment, no cap. π«Ά
β¨ SYNOPSIS β¨
void nvme_init_manage_export_nvms_send (struct libnvme_passthru_cmd *cmd
, __u8 sel , __u8 mos , __u16 mose , bool esubidv , __u16 esubid , void
*data , __u32 len );
π ARGUMENTS π
cmdβ Passthru command to use. This is the buffer bestie you're initializing. β¨selβ Select (SEL): management operation to perform, seeenum nvme_manage_export_nvms_send_sel. πmosβ Management Operation Specific (MOS): specific tosel. πmoseβ Management Operation Specific Extended (MOSE): specific tosel. π¦esubidvβ Exported NVM Subsystem Identifier Valid (ESUBIDV): if set,esubididentifies the target Exported NVM Subsystem; otherwise the target is identified by theSUBNQNindata. π₯esubidβ Exported NVM Subsystem Identifier (ESUBID), used ifesubidvis set. πdataβ Pointer to data buffer. πlenβ Length of data. π
π DESCRIPTION π
Initializes the passthru command buffer for the Manage Exported NVM Subsystem Send command. literally that's it, and she ate. π
okay that's the page! cute little sign-off: this is from the libnvme API manual, dated October 2026, and the footer carries that chaotic nvme_init_manage_export_nvmnvme_init_m...rt_nvms_send(9) string. iconic. πβ¨
π¦ 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