nvme_direct...tream_status(2)

💖 nvme_directive_recv_stream_status — bestie edition 💖

okay so you're in the libnvme API manual, section 2, and today's main character is nvme_directive_recv_stream_status. yes the whole page title is a mouthful — it's the Directive receive stream status call, and honestly? she's iconic, she's specific, and she's about to tell you which streams your namespace is vibing with. 🦋

---

✨ NAME ✨

nvme_directive_recv_stream_status — Directive receive stream status 💅

---

🌸 SYNOPSIS 🌸

int nvme_directive_recv_stream_status (int fd , __u32 nsid , unsigned int nr_entries , struct nvme_streams_directive_status *id );

lowkey a lot of arguments but we're gonna walk through each one, no cap 🫶

---

🎀 ARGUMENTS 🎀

• fd — the file descriptor of your nvme device. this is your all-access pass, the little int that says "yeah i know this drive personally" 🔥
• nsid — Namespace ID. which namespace are we talking to? that one. exactly that one. ✨
• nr_entries — number of streams to receive. so like, how many you're asking for. not more, not less, fr fr.
• id — the stream status buffer. this is where the tea gets poured in — a struct nvme_streams_directive_status * shaped cup 🍓

---

💀 RETURN 💀

so here's the vibe check: you get back the nvme command status if a response was received — go peek at enum nvme_status_field for the deets on what those statuses mean, iykyk 👑

and if no response came through? then it's -1 and errno is set. that's the "something went sideways, check errno bestie" path 😭

not me being dramatic but like — always check the return value. every single time. periodt.

---

this page lives in the libnvme API manual, and the source/version tag down at the bottom is libnvme, dated July 2026. so yeah, that's the whole scroll. go forth and read those streams, queen 👑💖