rdma_rw_mr_factor(9)

💫 NAME 💫

rdma_rw_mr_factor — bestie, this one literally just tells you how many MRs you need for a payload ✨

🦋 SYNOPSIS 🦋

unsigned int rdma_rw_mr_factor(struct ib_device *device, u32 port_num,
                               unsigned int maxpages);

🎀 ARGUMENTS 🎀

• device — the device that's handling the connection, okurrr 🫶
• port_num — the port num your connection is bound to, iykyk
• maxpages — the maximum payload pages per rdma_rw_ctx 📄

👑 DESCRIPTION 👑

okay so, rdma_rw_mr_factor returns the number of MRs that your device requires to move maxpayload bytes. no cap, that's the whole vibe 💅

and like, the value it hands back isn't just for show — it gets used during transport creation to compute max_rdma_ctxts and the size of the transport's Send and Send Completion Queues. so it's giving lowkey foundational, fr fr 🔥

🌈 SEE ALSO 🌈

• the kernel file ./drivers/infiniband/core/rw.c — go read it, it's iconic 💖
• rdma_rw_ctx_init(9)
• rdma_rw_ctx_init_bvec(9)
• rdma_rw_ctx_signature_init(9)
• rdma_rw_ctx_wrs(9)
• rdma_rw_ctx_post(9)
• rdma_rw_ctx_destroy(9)
• rdma_rw_ctx_destroy_bvec(9)
• rdma_rw_ctx_destroy_signature(9)
• rdma_rw_max_send_wr(9)

and that's the whole page, bestie 🧚 mwah 💋 — brought to you by ./drivers/infiniband/core, dated October 2026, and yes the page itself is rdma_rw_mr_factor(9) slay 💅✨