NVME_IDENTIFY_ENDURANCE_GROUP_LIST(2)

✨ nvme_identify_endurance_group_list β€” the libnvme API manual πŸ’–

okay bestie, so we're in the libnvme API manual and this one is literally called nvme_identify_endurance_group_list. yes the actual manual page header shortens it to nvme_identif...e_group_list(2) because apparently even man pages get truncated, slay. anyway.


πŸ¦‹ NAME πŸ¦‹

nvme_identify_endurance_group_list β€” it's giving Endurance group list data ✨

🌸 SYNOPSIS 🌸

int nvme_identify_endurance_group_list (int fd , __u16 endgrp_id ,
       struct nvme_id_endurance_group_list *list );

like, three args, one return value, no notes. iconique.

πŸŽ€ ARGUMENTS πŸŽ€

  • fd β€” the file descriptor of the nvme device, aka your little golden ticket to the hardware, no cap πŸ’…
  • endgrp_id β€” the endurance group identifier, a __u16, so it knows which endurance group we're talking about 🫢
  • list β€” an array of endurance group identifiers, pointing at a struct nvme_id_endurance_group_list, which is where the good stuff lands ⭐

πŸ’œ RETURN πŸ’œ

so here's the tea: you get the nvme command status if a response was received β€” go peek at enum nvme_status_field for what all those values actually mean, iykyk.

and if not? you get -1 with errno set instead. 😭 literally the classic "something went sideways" combo, fr fr.

not me having to remind you that -1 + errno is a failure and the status field is a response β€” they are not the same vibe, bestie, do not conflate them πŸ’€

July 2026 energy, libnvme API manual teaaa πŸ“ β€” that's the version and the date this page came from, and that's the whole thing. you ate. periodt. πŸ‘‘βœ¨

πŸ“¦ where this page comes from