rdma_user_mmap_entry_insert(9)

📦 version 7.3.1, in nixpkgs unstable

💅 rdma_user_mmap_entry_insert(9) — the Kernel API Manual, but make it make sense

okay so bestie, welcome to the rdma_user_mmap_entry_insert page from the Kernel API Manual ✨ this is the one that slides a new entry into the mmap_xa database, and honestly? iconic behavior.

🌸 NAME 🌸

rdma_user_mmap_entry_insert — insert an entry to the mmap_xa, fr fr 🫶

✨ SYNOPSIS ✨

int rdma_user_mmap_entry_insert (struct ib_ucontext *ucontext , struct
       rdma_user_mmap_entry *entry , size_t length );

🎀 ARGUMENTS 🎀

  • ucontext — the user context it's associated with 💫
  • entry — literally the entry we're inserting into the mmap_xa, that's the whole vibe
  • length — length of the address that will be mmapped 📏

🦋 DESCRIPTION 🦋

So here's the tea ☕: this function should be called by drivers that use the rdma_user_mmap interface for handling user mmapped addresses. The database itself is handled in the core, and helper functions are provided to insert entries into the database and extract entries when the user calls mmap with the given offset.

The function allocates a unique page offset that should be provided to user 👈 and the user will use that offset to retrieve information such as address to be mapped and how. it's giving "here's your little ticket, go get your info" 🎟️

🔥 RETURN 🔥

0 on success and -ENOMEM on failure 💀 (classic).

👑 SEE ALSO 👑

the whole friend group, together at last 💜

ngl bestie, there's no bug note or warning on this page — it's just a clean little insert function doing its main character thing 🌈

and that's the page!! 🎀 mwah 💋 this one comes to you from ./drivers/infiniband/core, dated October 2026, and it's rdma_user_mmap_entry_insert(9) — go forth and mmap responsibly, bestie 🧚⭐

📦 where this page comes from