libnvme_submit_io_passthru(9)

📦 version 3.2, in arch rolling

💅 libnvme_submit_io_passthru — the libnvme API manual, but make it make sense

okay so bestie, welcome to the libnvme_submit_io_passthru(9) page ✨ this is the libnvme API manual and honestly? it's a short one. we love a concise icon. 🎀

🌸 NAME 🌸

libnvme_submit_io_passthru — literally just queues up an IO passthru command. that's the whole vibe. 🦋

✨ SYNOPSIS ✨

int libnvme_submit_io_passthru (struct libnvme_transport_handle *hdl ,
struct libnvme_passthru_cmd *cmd , void *cookie );

three args, one int back. it's giving "small function, big responsibility" ngl 💅

🫶 ARGUMENTS 🫶

  • hdl — the transport handle. your little connection bestie, the thing that actually knows how to talk to the device. 🔌
  • cmd — the nvme IO command you're sending. this is the main character of the whole operation, fr fr 👑
  • cookie — a user-defined opaque value that gets returned at completion. yes it's literally a cookie 🍓 — you hand it over, you get it back, it means whatever you want it to mean. iykyk.

💖 DESCRIPTION 💖

so here's the tea: this queues cmd for asynchronous execution. ⚡ you don't sit there waiting and waiting (not me refreshing the terminal 😭) — you fire it off and go live your life.

completion gets reported via libnvme_reap_passthru. so like, that's where you actually pick up your results. don't forget to reap, bestie, or you'll just be out here wondering where your command went 🙈

🔥 RETURN 🔥

  • 0 — successful queueing. slay. ✅
  • negative error code — otherwise. 💀 (yes, negative. that's your red flag moment, check the value.)
no cap: 0 only means it got queued, not that the command finished. that's what the reaping is for. ⭐

and that's the whole page, bestie, you ate that 🧚 this was the libnvme_submit_io_passthru(9) entry from the libnvme API manual, dated October 2026 — go forth and queue responsibly 💜🌈

📦 where this page comes from