NVME_INIT_IDENTIFY_UUID_LIST-LIBNVME3(2)
π 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
- 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