rpcrdma_rn_register(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– rpcrdma_rn_register(9) πŸ’–

okay bestie, welcome to the Kernel API Manual page for rpcrdma_rn_register(9) β€” yes, the whole device removal notification situation, and we're gonna make it make sense πŸ’…βœ¨


✨ NAME ✨

rpcrdma_rn_register - register to get device removal notifications πŸŽ€

πŸ¦‹ SYNOPSIS πŸ¦‹

here's the signature, bestie β€” keep the punctuation exactly as it is, it's iconic:

       int rpcrdma_rn_register (struct ib_device *device , struct
       rpcrdma_notification *rn , void (*done)(struct rpcrdma_notification *rn)
       );

πŸ’… ARGUMENTS πŸ’…

  • device β€” device to monitor πŸ‘€
  • rn β€” notification object that wishes to be notified 🫢
  • done β€” callback to notify caller of device removal πŸ“£

🌸 DESCRIPTION 🌸

Returns zero on success. The callback in rn_done is guaranteed to be invoked when the device is removed, unless this notification is unregistered first. no cap βœ…

On failure, a negative errno is returned. rn->rn_done is left NULL on every failure path (it is armed before xa_alloc but cleared again if xa_alloc fails), so the rn may safely be passed to rpcrdma_rn_unregister without a separate registered/unregistered flag in the caller. periodt πŸ’…

bestie note: that NULL on every failure path is the whole safety vibe β€” it means the caller doesn't need its own registered/unregistered flag. 🫑

πŸ”₯ SEE ALSO πŸ”₯

go peek at these, bestie πŸ‘‘:


mwah πŸ’‹ this page lives under ./net/sunrpc/xprtrdma, stamped October 2026, and it's the rpcrdma_rn_register(9) manpage from the Kernel API Manual. periodt 🫢🌈

πŸ“¦ where this page comes from