NVME_INIT_MANAGE_EXPORT_NVMS_SEND_SET_CONFIG_STATE-LIBNVME3(2)

πŸ“¦ version 3.2, in arch rolling

πŸ’– NAME πŸ’–

nvme_init_manage_export_nvms_send_set_config_state β€” bestie, say that five times fast, I dare you 😭 β€” this is the one that initializes a passthru command for Manage Exported NVM Subsystem Send - Set Exported Configuration State. Yes, that's the whole name. She's long but she's iconic πŸ‘‘

This page lives in the libnvme API manual, section 9, and honestly the function name alone is a whole mood.


✨ SYNOPSIS ✨

void nvme_init_manage_export_nvms_send_set_config_state (struct
libnvme_passthru_cmd *cmd , bool esubidv , __u16 esubid , void *data ,
__u32 len );

Returns void, so like… no exit codes to worry about, she just does the thing and dips πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • cmd β€” the passthru command you're setting up. This is the vessel, the main character, the thing getting initialized 🫢
  • esubidv β€” Exported NVM Subsystem Identifier Valid (ESUBIDV). If it's set, then esubid is the one that identifies the target Exported NVM Subsystem. If it's not set, the target gets identified by the SUBNQN in data instead. So basically this bool is the "trust me, use the ID" switch 🌸
  • esubid β€” Exported NVM Subsystem Identifier (ESUBID), and it only gets used if esubidv is set. No esubidv, no esubid moment, periodt βœ‹
  • data β€” the Exported NVM Subsystem Template specific configuration state data buffer. This is where your actual payload hangs out πŸ’œ
  • len β€” length of data. Gotta tell her how much to read, obviously πŸ¦‹

🌈 DESCRIPTION 🌈

Okay so what this does: it 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_SET_CONFIG_STATE ⭐

Heads up though, bestie πŸ‘€ β€” if it fails with status NVME_SC_INVALID_EXPORTED_CONFIG_STATE, the location of the first invalid bit comes back to you in the CQE result. Check out enum nvme_export_nvms_set_config_state_cqe_dw0 for the details. That's your "which bit was it" receipt 🧾

πŸ¦‹ SEE ALSO πŸ¦‹

Honestly the only cross-reference on this page is that enum nvme_export_nvms_set_config_state_cqe_dw0, and it's already living up in DESCRIPTION β€” so go peek at it if you're hunting down that first invalid bit πŸ”₯


and that's the whole page, bestie πŸ’– this glorious mouthful of a function comes to you straight from the libnvme API manual, dated October 2026, and the source line is literally the same tragically-long name: nvme_init_manage_export_nvms_send_set_config_state(9) πŸŽ€ go forth and set those configuration states, iykyk πŸ§šβ€β™€οΈπŸ’…

πŸ“¦ where this page comes from