NVME_GET_FEATURES_NUM_QUEUES(2)

✨ nvme_get_features_num_queues 💅

okay bestie, welcome to the nvme_get_features_num_queues page from the libnvme API manual — she's a section 2 girlie and she's here to fetch the number of queues feature for you. no cap. 🎀

---

🌸 NAME 🌸

nvme_get_features_num_queues — literally just Get number of queues feature. that's the whole vibe. 👑

---

🦋 SYNOPSIS 🦋

int nvme_get_features_num_queues (int fd , enum nvme_get_features_sel
sel , __u32 *result );

she takes three things and gives you back an int. iconic behavior honestly. ✨

---

💖 ARGUMENTS 💖

• fd — the File descriptor of nvme device. that's your lil ticket to the device, your backstage pass, your main character handle. 🎟️
• sel — Select which type of attribute to return, see enum nvme_get_features_sel. so like, which flavor of attribute do you want back? the enum has the options, go look at it. 👀
• result — The command completion result from CQE dword0. yes bestie, dword0 specifically, the literal first dword of the completion queue entry. she's precise like that. 💅

---

🔥 RETURN 🔥

so here's the tea: you get back the nvme command status if a response was received (see enum nvme_status_field) or -1 with errno set otherwise. 😭

translation bestie: you either get a real status back from the command, or you get -1 and errno is set. don't sleep on checking errno, fr fr.

---

💜 SEE ALSO 💜

(okay the original doesn't hand us a SEE ALSO list, so like... go peek at enum nvme_get_features_sel and enum nvme_status_field, they're the referenced girlies here 🫶)

---

🧚 reminder bestie: every option, arg, and number above is exactly as the page says it. no improvising, no guessing at behavior. iykyk. 🌈

---

author signing off: this lil slice of documentation comes from the libnvme API manual, dated July 2026, and she's filed under nvme_get_features_num_queues(2) in section 2. slay, study her, and go get those queue counts. 🎀✨🌟💜