rvt_create_mmap_info(9)

okay bestie, welcome to the rvt_create_mmap_info(9) page from the Kernel API Manual — this one is all about allocating info for hfi1_mmap, and we’re gonna get through it together 💖✨

🌸 NAME 🌸

rvt_create_mmap_info — allocate information for hfi1_mmap

🦋 SYNOPSIS 🦋

struct rvt_mmap_info * rvt_create_mmap_info (struct rvt_dev_info *rdi ,
       u32 size , struct ib_udata *udata , void *obj );

🎀 ARGUMENTS 🎀

• rdi — the rvt dev struct, aka the main character of this function’s little world 👑
• size — size in bytes to map, so like… how much we’re mapping, bestie 📏
• udata — user data, and heads up: it must be valid! not optional, not “maybe later,” valid fr fr 😭
• obj — opaque pointer to a cq, wq etc — mysterious, iconic, we don’t peek inside 💅

⭐ RETURN ⭐

On success you get an rvt_mmap struct, slay 🫶 On failure you get ERR_PTR, which is the “nope, something went wrong” vibe check 💀

🌈 SEE ALSO 🌈

• Kernel file ./drivers/infiniband/sw/rdmavt/mmap.c
• rvt_mmap_init(9)
• rvt_release_mmap_info(9)
• rvt_mmap(9)
• rvt_update_mmap_info(9)

and that’s the whole page, bestie ✨ this one comes from ./drivers/infiniband/sw/rdmavt, dated October 2026, and it’s literally rvt_create_mmap_info(9) — periodt 💜🎀