NVME_GET_LOG_SUPPORT_CAP_CONFIG_LIST(2)

πŸ’– nvme_get_log_support_cap_config_list β€” bestie edition πŸ’–

okay so like, we're in the libnvme API manual, section 2 (that's the syscall/function section, iykyk), and today's main character is nvme_get_log_support_cap_config_list. yes the name is long. yes you will type it wrong the first time. it's fine, we believe in you 🫢


✨ NAME ✨

nvme_get_log_support_cap_config_list β€” Retrieve Supported Capacity Configuration List

that's it. that's the whole job. go get the list of capacity configurations your NVMe device is out here supporting, periodt. πŸ’…


🌸 SYNOPSIS 🌸

int nvme_get_log_support_cap_config_list (int fd , __u16 domid , struct
nvme_supported_cap_config_list_log *cap );

three things in, one int out. classic. the way that it takes a struct pointer and writes into it? obsessed. 😭


πŸŽ€ ARGUMENTS πŸŽ€

  • fd β€” File descriptor of the nvme device. it's giving "your ticket to the device", fr fr. no fd, no log, no nothing. πŸ’€
  • domid β€” Domain Identifier selection, if supported. keyword: if supported. if your device isn't about that domain life, don't come crying to the manpage. πŸ™ˆ
  • cap β€” User address to store supported capabilities config list. this is where the goods land. you hand over somewhere to put a struct nvme_supported_cap_config_list_log, and it does the thing. lowkey the whole point of the function ngl. ✨

⭐ RETURN ⭐

so what do you get back? it returns the nvme command status if a response was received β€” peep enum nvme_status_field for the full menu of possible statuses, bestie, there's a lot of them and they all mean something specific, ok? πŸ‘‘

and if there was no response? it's -1, with errno set. so like, check errno, that's your receipt. 🧾

πŸ’– reminder: status got a response = nvme command status. error got no response = -1 + errno set. two completely different moods, don't mix them up.

and that's the whole page, you ate that 🌈 go forth, call your function, retrieve your capacity configuration list. iconic behaviour honestly. πŸ¦‹

nvme_get_log..._config_list(2) β€” libnvme API manual β€” July 2026 πŸ’œ mwah, signing off, drink water, read your manpages

πŸ“¦ where this page comes from