rpcrdma_unpin_rqst(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… rpcrdma_unpin_rqst(9) πŸ’…

okay bestie, welcome to the Kernel API Manual entry for rpcrdma_unpin_rqst β€” yes that's the manual section 9, we're in kernel-land now 🧚✨


🌸 NAME 🌸

rpcrdma_unpin_rqst β€” release an rqst without completing it 🫢


✨ SYNOPSIS ✨

void rpcrdma_unpin_rqst (struct rpcrdma_rep *rep );

that's it. that's the whole signature. no cap, it returns void β€” nothing comes back, she just does her thing and leaves πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • rep β€” the RPC/RDMA Receive context πŸ‘‘ this is the thing you're handing over, bestie, so treat it right

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the vibe: you call this when the connection is lost 😭 and you need a Reply to be dropped, so that its matching Call can be retransmitted later on a new connection πŸ”₯

it's giving cleanup era. the Reply doesn't get completed, it gets released β€” very much on purpose, very much the point. the way that retransmission gets to happen is literally because you unpinned this rqst first. iykyk πŸ§šβ€β™€οΈ

heads up: this is the "connection is gone" path, so don't be out here expecting a normal completion β€” the whole point is that the Reply gets dropped, not finished πŸ’€

⭐ SEE ALSO ⭐

like a whole friend group of rpcrdma_* functions β€” go say hi πŸŒˆπŸ’–


and that's the page, bestie!! this one lives under ./net/sunrpc/xprtrdma and it's dated October 2026 β€” so yeah, freshly stamped, slay πŸŒΈβœ¨πŸŽ€ see u in the next manpage πŸ’œ

πŸ“¦ where this page comes from