rvt_post_srq_recv(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ rvt_post_srq_recv(9) πŸŽ€

okay bestie, so this is a page straight out of the Kernel API Manual, and it's all about rvt_post_srq_recv β€” the little function that gets your receive posted on a shared receive queue. it's short, it's sweet, and honestly it's giving "small but crucial" energy. let's get into it πŸ’…


✨ NAME ✨

rvt_post_srq_recv β€” post a receive on a shared receive queue πŸ¦‹


🌸 SYNOPSIS 🌸

int rvt_post_srq_recv (struct ib_srq *ibsrq , const struct ib_recv_wr
*wr , const struct ib_recv_wr **bad_wr );

like… the whole signature, exactly as it lives in the headers. copy it, don't touch it, periodt πŸ’–


πŸ’œ ARGUMENTS πŸ’œ

  • ibsrq β€” the SRQ you're posting the receive on. this is your queue, your moment, your main character ✨
  • wr β€” the list of work requests to post. plural! it's a whole list, not just one, and we love her for that 🫢
  • bad_wr β€” a pointer to the first WR that causes a problem gets put in here. so if something goes wrong, this is where the drama gets reported πŸ’€

πŸ”₯ DESCRIPTION πŸ”₯

so here's the little detail that matters: this may be called from interrupt context. yes, interrupt context. no cap. handle it accordingly, bestie 😭


🌈 RETURN 🌈

0 on success, else errno. that's it. that's the whole vibe check 😌


πŸ‘‘ SEE ALSO πŸ‘‘

and now for the friend group β€” the kernel file ./drivers/infiniband/sw/rdmavt/qp.c and literally all of these iconic siblings:


okay that's the whole page, ily, go post some receives responsibly πŸ§šπŸ’–

this little number lives over in ./drivers/infiniband/sw/rdmavt and it's dated October 2026 β€” so yeah, shoutout to the source, the version, and the date, they ate πŸ“β­

πŸ“¦ where this page comes from