NVME_INIT_IDENTIFY_DOMAIN_LIST-LIBNVME3(2)
π nvme_init_id..._domain_list(9) β libnvme API manual, bestie edition π
okay so this is one of those little function pages from the libnvme API manual, section 9, and honestly? she's short, she's sweet, she does exactly one thing. let's get into it β¨
πΈ NAME πΈ
nvme_init_identify_domain_list β Initialize passthru command for Domain list
like... that's it, that's her whole job. she sets up the passthru command so you can go get the Domain list. slay. π
β¨ SYNOPSIS β¨
void nvme_init_identify_domain_list (struct libnvme_passthru_cmd *cmd ,
__u16 domid , struct nvme_id_domain_list *list );
three args, returns void, no drama. copy it exactly, don't get creative with it π«Ά
π¦ ARGUMENTS π¦
cmdβ the Command data structure you're initializing. this is the one getting set up, bestie, hand her over πdomidβ the Domain ID. it's a__u16, it's the domain, it's giving very specific πlistβ the user space destination address where the data gets transferred. yes, your memory, your problem, so make sure it's real π
π DESCRIPTION π
ngl this one's a one-liner and I respect it. it initializes the passthru command buffer for the Identify command, and it does that with the CNS value NVME_IDENTIFY_CNS_DOMAIN_LIST.
so: passthru command buffer β initialized β Identify command β CNS NVME_IDENTIFY_CNS_DOMAIN_LIST. iconic, no cap, that's the whole vibe check β
fr fr do not go inventing your own CNS value here β the whole point is that this function already picked it for you π
π§ sign-off π§
and that's the page!! this lil cutie comes from the libnvme API manual and the date on it is October 2026 β so yeah, go forth and initialize your domain lists, main character energy only πππ·
π¦ 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