rpcrdma_req_create(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

rpcrdma_req_create(9) β€” Kernel API Manual πŸ’…

Okay so bestie, welcome to the Kernel API Manual page for rpcrdma_req_create(9) β€” it’s giving β€œallocate the thing” energy and we’re gonna read it together, no cap 🫢


✨ NAME ✨

rpcrdma_req_create β€” allocate an rpcrdma_req object πŸ’–


🌸 SYNOPSIS 🌸

struct rpcrdma_req * rpcrdma_req_create (struct rpcrdma_xprt *r_xprt ,
size_t size );

πŸŽ€ ARGUMENTS πŸŽ€

  • r_xprt β€” the controlling r_xprt πŸ‘‘
  • size β€” the initial size, in bytes, of send and receive buffers 🧚

πŸ¦‹ DESCRIPTION πŸ¦‹

Bestie, this one is short and iconic: it returns an allocated and fully initialized rpcrdma_req or NULL πŸ’€βœ¨ That’s the whole plot. No extra lore, no side quests β€” just an allocated and fully initialized rpcrdma_req or NULL, periodt πŸ’…


πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./net/sunrpc/xprtrdma/verbs.c is where the lore lives, and the related manual pages are: rpcrdma_flush_disconnect(9), rpcrdma_wc_send(9), rpcrdma_wc_receive(9), rpcrdma_cm_event_handler(9), rpcrdma_xprt_connect(9), rpcrdma_xprt_disconnect(9), rpcrdma_sendctx_get_locked(9), rpcrdma_sendctx_unget_locked(9), rpcrdma_sendctx_put_locked(9), rpcrdma_mrs_refresh(9), rpcrdma_req_setup(9), rpcrdma_rep_put(9), rpcrdma_buffer_create(9), rpcrdma_req_destroy(9), rpcrdma_mrs_destroy(9), rpcrdma_buffer_destroy(9), rpcrdma_mr_get(9), rpcrdma_reply_put(9), rpcrdma_buffer_get(9), rpcrdma_buffer_put(9), rpcrdma_regbuf_realloc(9), __rpcrdma_regbuf_dma_map(9), rpcrdma_post_recvs(9) πŸ’–βœ¨


This iconic page came from ./net/sunrpc/xprtrdma, dated October 2026, and its manual title is rpcrdma_req_create(9) β€” slay and goodbye, bestie πŸŽ€πŸ’…

πŸ“¦ where this page comes from