NVME_INIT_IDENTIFY_NVMSET_LIST-LIBNVME3(2)

📦 version 3.2, in arch rolling

💅 nvme_init_identify_nvmset_list(9) — libnvme API manual 🦋

okay so bestie, welcome to the libnvme API manual, section 9, and today's main character is nvme_init_identify_nvmset_list ✨

🎀 NAME 🎀

nvme_init_identify_nvmset_list — the glow-up function that initializes the passthru command for the NVM Set List data structure 💖

🌸 SYNOPSIS 🌸

void nvme_init_identify_nvmset_list (struct libnvme_passthru_cmd *cmd ,
__u32 nsid , __u16 nvmsetid , struct nvme_id_nvmset_list *nvmset );

like yes, she returns nothing (void) — she just sets things up and leaves, iconic behavior honestly 👑

✨ ARGUMENTS ✨

  • cmd — the command data structure you're initializing 🫶 this is the one getting prepped for the glow-up
  • nsid — the Namespace identifier, __u32, no cap
  • nvmsetid — the NVM Set Identifier, __u16, tiny but mighty 🍓
  • nvmset — the user space destination address where the data gets transferred 💫

🔥 DESCRIPTION 🔥

So what she actually does: she initializes the passthru command buffer for the Identify command, with the CNS value set to NVME_IDENTIFY_CNS_NS_ACTIVE_LIST ⭐

that's it, that's the whole vibe. the command buffer gets its passthru setup, CNS gets NVME_IDENTIFY_CNS_NS_ACTIVE_LIST, and your nvmset destination is ready for the data to land 🌈 slay.

ngl bestie, don't skip the argument order — cmd, nsid, nvmsetid, nvmset — you know how the compiler gets when you mix up your __u16 and your __u32 😭💀

mwah 💋 that's the whole page — courtesy of the libnvme API manual, dated October 2026. go forth and identify those NVM Sets, periodt 🧚💜

📦 where this page comes from