rpcrdma_rn_register(9)
π 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 π:
- Kernel file
./net/sunrpc/xprtrdma/ib_client.c rpcrdma_rn_unregister(9)rpcrdma_add_one(9)rpcrdma_remove_one(9)rpcrdma_ib_client_unregister(9)rpcrdma_ib_client_register(9)
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms