frwr_map(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

frwr_map(9) πŸ’–

okay so bestie, this page is from the Kernel API Manual and it's all about frwr_map β€” registering a memory region from an xdr_buf cursor. it's giving kernel memory registration main character energy, no cap. let's get into it ✨

🌸 NAME 🌸

frwr_map β€” literally registers a memory region from an xdr_buf cursor. periodt. πŸ’…

✨ SYNOPSIS ✨

int frwr_map (struct rpcrdma_xprt *r_xprt , struct rpcrdma_xdr_cursor
*cur , bool writing , __be32 xid , struct rpcrdma_mr *mr );

πŸŽ€ ARGUMENTS πŸŽ€

  • r_xprt β€” the controlling transport πŸš‚
  • cur β€” cursor tracking position within the xdr_buf πŸ“
  • writing β€” true when RDMA Write will be used ✍️
  • xid β€” XID of RPC using the registered memory πŸ†”
  • mr β€” MR to fill in 🧁

πŸ’… DESCRIPTION πŸ’…

so what this actually does: prepare a REG_MR Work Request to register a memory region for remote access via RDMA READ or RDMA WRITE. iconic behavior honestly. πŸ‘‘

it returns 0 on success β€” cursor advanced past consumed data and mr populated β€” or a negative errno on failure. πŸ˜­πŸ’€

πŸ¦‹ SEE ALSO πŸ¦‹


and that's the whole page, bestie 🫢 this one lives at source path ./net/sunrpc/xprtrdma, dated October 2026, and it's literally frwr_map(9). periodt. πŸ’–βœ¨

πŸ“¦ where this page comes from