NVME_INIT_IDENTIFY_UUID_LIST-LIBNVME3(2)

πŸ“¦ version 3.2, in arch rolling

πŸ’… nvme_init_identify_uuid_list β€” libnvme API manual, bestie edition ✨

okay so this is a page from the libnvme API manual, and honestly? it's a little icon and it does exactly one thing. let's get into it πŸŽ€


✨ NAME ✨

nvme_init_identify_uuid_list β€” initializes the passthru command for the UUID list. that's it, that's the whole job, and she does it flawlessly πŸ‘‘


πŸ¦‹ SYNOPSIS πŸ¦‹

void nvme_init_identify_uuid_list (struct libnvme_passthru_cmd *cmd ,
struct nvme_id_uuid_list *uuid_list );

like, look at her. two arguments, returns nothing (void), zero drama. we love a low-maintenance queen πŸ’–


🌸 ARGUMENTS 🌸

  • cmd β€” the command data structure you're gonna initialize. this is the main character right here, she's getting set up 🫢
  • uuid_list β€” the user space destination address where the data gets transferred. think of it as the cute little drop-off spot for your bytes πŸ“¦

πŸ”₯ DESCRIPTION πŸ”₯

so what does she actually do? she initializes the passthru command buffer for the Identify command, with the CNS value set to NVME_IDENTIFY_CNS_UUID_LIST. no cap, that's the whole vibe β€” buffer goes in, Identify command comes out, CNS value is literally NVME_IDENTIFY_CNS_UUID_LIST periodt πŸ’…

if you were wondering "is there a hidden twist?" β€” nope! not me overcomplicating it. it's giving "one job, done right" energy 🌈


ngl bestie, if you're calling this you probably already know what NVME_IDENTIFY_CNS_UUID_LIST means. if you don't β€” that's a you and your NVMe spec situation, not a this-manpage situation πŸ™ˆ

and that's the page! source and version stay tucked in the footer like always, dated October 2026, from the libnvme crew β€” mwah, thanks for the API, she's iconic πŸ‘‘πŸ’œβ­

πŸ“¦ where this page comes from