libnvme_reap_passthru(9)

📦 version 3.2, in arch rolling

💅 libnvme_reap_passthru — the libnvme API manual, bestie edition 🎀

okay so real quick, this page lives in the libnvme API manual and it's about libnvme_reap_passthru(9) — yes the whole name, we're not abbreviating, she's an icon and she knows it ✨

🌸 NAME 🌸

libnvme_reap_passthru — reap one async completion. literally just one. one single completion. she's not greedy 💅

🦋 SYNOPSIS 🦋

int libnvme_reap_passthru (struct libnvme_transport_handle *hdl , struct
libnvme_passthru_completion *completion );

like copy that exactly, no touchy, character for character, iykyk 🫶

🎀 ARGUMENTS 🎀

  • hdl — the transport handle. your little handle bestie, she carries the transport vibes 💖
  • completion — the completion output structure. this is where the good stuff gets written back, so don't skimp on it 🍓

🔥 DESCRIPTION 🔥

So the way that this works: libnvme_reap_passthru waits for one queued passthru command to complete ⏳ — yes, it actually blocks and waits, she's patient like that — and then it stashes three things into completion:

  • the completed command pointer 👑
  • the associated cookie 🍪 (not a real cookie, sorry bestie 😭)
  • the completion status ⭐

All three go into completion. That's the whole assignment. main character energy, minimal drama, no cap 💜

🌈 RETURN 🌈

  • 0 on success — slay, we ate 💅
  • a negative error code otherwise — not slay, but at least you know 💀
lowkey reminder: the return value is int, so the successful case is 0, and anything negative means something went sideways — check it, fr fr 🙈

that's the whole page bestie, mwah 💖

this cutie was brought to you by libnvme — page libnvme_reap_passthru, from the libnvme_reap_passthru(9) manual, dated October 2026 🧚‍♀️ see you in the next man page, periodt ✨🦋

📦 where this page comes from