NVME_GET_FEATURES_IRQ_COALESCE(2)

💖 nvme_get_features_irq_coalesce — bestie edition 💖

okay so this is a page from the libnvme API manual, section 2, and the star of the show is nvme_get_features_irq_coalesce(2). yes it's a whole mouthful, yes it's iconic, no we are not shortening it, it's literally the name. 💅

---

✨ NAME ✨

nvme_get_features_irq_coalesce — get the IRQ coalesce feature 🎀

like. that's the whole job. it goes and gets it. no cap.

---

🌸 SYNOPSIS 🌸

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

three things go in, an int comes out. that's the vibe. 🦋

---

🫶 ARGUMENTS 🫶

• fd — the file descriptor of your nvme device. this is your ticket in, your little backstage pass. no fd, no feature, periodt.
• sel — selects which type of attribute you want back. check enum nvme_get_features_sel for the menu, bestie, it's giving build-your-own-feature. ✨
• result — the command completion result from CQE dword0. that's where the answer lands. it's a __u32 *, so it's a pointer, so yes it writes through it, we love a pointer moment. 💜

---

⭐ RETURN ⭐

so here's what you get back:

• the nvme command status if a response was received — peep enum nvme_status_field for the whole roster of what that could be 👑
• or -1, with errno set, in every other case 😭

lowkey important: -1 is not a status, it's a "we didn't even get a response" situation. check errno when you see it. fr fr.

---

🌈 SEE ALSO 🌈

ngl bestie the original doesn't list any SEE ALSO refs here — but you've got enum nvme_get_features_sel and enum nvme_status_field living in the headers, and those two are your ride-or-dies for this call 🧚

---

that's the whole page, no filler, no gatekeeping 🍓

signing off with love from the libnvme API manual, dated July 2026, brought to you by nvme_get_features_irq_coalesce(2) — go get that feature, bestie, you ate 💖✨🎀