nvme_init_m...rt_nvms_send(9)

πŸ“¦ version 3.2, in arch rolling

🌸 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, see enum nvme_manage_export_nvms_send_sel. πŸ‘‘
  • mos β€” Management Operation Specific (MOS): specific to sel. πŸŽ€
  • mose β€” Management Operation Specific Extended (MOSE): specific to sel. πŸ¦‹
  • esubidv β€” Exported NVM Subsystem Identifier Valid (ESUBIDV): if set, esubid identifies the target Exported NVM Subsystem; otherwise the target is identified by the SUBNQN in data. πŸ”₯
  • esubid β€” Exported NVM Subsystem Identifier (ESUBID), used if esubidv is 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