rvt_post_recv(9)

📦 version 7.3.1, in nixpkgs unstable

💖 rvt_post_recv(9) — like, the Kernel API Manual page, but make it make sense 💖

okay bestie, so this one's from the Kernel API Manual (yes, the rvt_post_recv(9) one, the section-9 girlie herself) and it's genuinely short and sweet. Let's get into it ✨

🌸 NAME 🌸

rvt_post_recv — post a receive on a QP 🫶

✨ SYNOPSIS ✨

int rvt_post_recv (struct ib_qp *ibqp , const struct ib_recv_wr *wr ,
const struct ib_recv_wr **bad_wr );

🎀 ARGUMENTS 🎀

  • ibqp — the QP you're posting the receive on. that's your girl, that's the target 💅
  • wr — the WR you're actually posting. the goods 📦
  • bad_wr — the first bad WR gets dropped in here. like a little shame corner for the misbehaving one 🙈

🦋 DESCRIPTION 🦋

This may be called from interrupt context. no cap, that's the whole thing — but it's kind of a big deal, so clock it 👑

⭐ RETURN ⭐

0 on success, otherwise errno. that's it, that's the vibe check ✅

🌈 SEE ALSO 🌈

Straight from the kernel file ./drivers/infiniband/sw/rdmavt/qp.c, here's the whole friend group, alphabetically unbothered, all in section 9:

💀 quick reminder babe: this is kernel-side stuff, so if you're calling it from interrupt context like the DESCRIPTION says, stay humble and stay careful. no cap.

and that's the page, bestie 🎀 sign-off time: it comes to you from ./drivers/infiniband/sw/rdmavt, dated October 2026, and yeah — it's rvt_post_recv(9) all the way down 💜✨

📦 where this page comes from