libnvme_exec_io_passthru(9)

💅 libnvme_exec_io_passthru — like, the whole manual page, bestie

okay so this is the libnvme_exec_io_passthru(9) page from the libnvme API manual, and honestly? it's a short one but she serves. let's get into it 🎀

---

✨ NAME ✨

libnvme_exec_io_passthru — submit an IO passthru command and wait for it, like a good little synchronous icon 🫶

---

🌸 SYNOPSIS 🌸

int libnvme_exec_io_passthru (struct libnvme_transport_handle *hdl ,
struct libnvme_passthru_cmd *cmd );

no cap, that's the whole signature. copy it exactly, she does not need your "improvements" 💀

---

🦋 ARGUMENTS 🦋

• hdl — your transport handle. the vibe carrier. the main character of the connection, fr fr ✨
• cmd — the nvme IO command you're sending. this is the thing doing the actual work 💅

---

🌈 DESCRIPTION 🌈

okay so this is synchronous command execution. like, you send it and you wait. no chasing, no "i'll text you later" — it blocks right there until the job's done. very committed of her 👑

⚠️ important caveat, do NOT skip this one: when io_uring is enabled, this shares the async queue. so lowkey please don't mix this with direct async API usage on the same handle — that's giving chaos and we don't want that energy 🙈

and if you're doing batching? use the async API exclusively. periodt. no sneaky sync calls in there, bestie 💀

---

⭐ RETURN ⭐

so what does she give you back? two possible vibes:

• the nvme command status if a response was actually received — check enum nvme_status_field for what the number means 👀
• a negative error code otherwise 😭 (yes, negative. that's how you know something went sideways)

---

🧚 tiny reminder before you go: that io_uring queue-sharing thing is real, it's not me being dramatic for once. same handle + mixed sync/async = bad vibes only.

---

and that's the page, bestie!! 🍓 this little gem is from the libnvme API manual, dated October 2026, and she's filed under libnvme_exec_io_passthru(9). slay, go execute some commands, ily 💜🏆