frwr_query_device(9)

📦 version 7.3.1, in nixpkgs unstable

💅 frwr_query_device

ok so this is a page from the Kernel API Manual (yes we're in kernel land today bestie, buckle up 🎀), and it's all about frwr_query_device — the little guy that gets a transport ready for FRWR. iykyk.

✨ SYNOPSIS ✨

int frwr_query_device (struct rpcrdma_ep *ep , const struct ib_device *device );

like literally that's the whole signature, no notes 👑

🫶 ARGUMENTS 🫶

  • ep — the endpoint you're filling in. this is the one getting the glow-up ✨
  • device — the RDMA device you're querying. we're asking it questions, respectfully 💅

🌸 DESCRIPTION 🌸

okay so when this works, it sets a whole bunch of fields on your endpoint. here's the full list, no cap, every single one:

  • ep->re_attr
  • ep->re_max_requests
  • ep->re_max_rdma_segs
  • ep->re_max_fr_depth
  • ep->re_mrtype

and the return values? here's the vibe check 😭

  • On success, it returns zero. iconic. we love a clean 0 💖
  • -EINVAL — the device does not support FRWR memory registration. tragic, honestly.
  • -ENOMEM — the device is not sufficiently capable for NFS/RDMA. it's giving "not enough main character energy" 💀

🦋 SEE ALSO 🦋

the whole friend group 🫶 — kernel file ./net/sunrpc/xprtrdma/frwr_ops.c plus:

and that's the page bestie!! 🌈 this one lives in ./net/sunrpc/xprtrdma and it's dated October 2026 — so yeah, she's from the future, we stan a forward-thinking queen 👑✨ go query some devices, love u, bye!! 💜🎀

📦 where this page comes from