STRUCT RDMA_RESTRACK_ENTRY(9)

💖 NAME 💖

okay bestie, this is the struct rdma_restrack_entry(9) page from the Kernel API Manual, and it is literally about metadata per-entry. That’s the whole vibe: per-entry metadata, no cap. ✨

---

✨ SYNOPSIS ✨

struct rdma_restrack_entry {
    bool valid;
    u8 no_track : 1;
    struct kref             kref;
    struct completion       comp;
    struct task_struct      *task;
    const char              *kern_name;
    enum rdma_restrack_type type;
    bool user;
    u32 id;
 };

---

🎀 Members 🎀

• valid — the validity indicator, bestie. It’s giving “is this entry valid or not.” 💅

Entries are filled during rdma_restrack_add, and freeing can be attempted during rdma_restrack_del.

For a real example of that, see mlx5 QPs with type MLX5_IB_QPT_HW_GSI. Iconic example behavior, honestly. 🦋

• no_track — “don’t add this entry to restrack DB” energy. This field marks an entry that doesn’t need to be added to the internal restrack DB and presented later to users at the nldev query stage.
• kref — protects destroy of the resource. 🛡️
• comp — signals that all consumers of the resource have completed their work. 🫶
• task — owner of the resource tracking entity.

There are two types of entities: created by user and created by kernel.

This is relevant for the entities created by users. For the entities created by kernel, this pointer will be NULL.

• kern_name — name of the owner for the kernel-created entities.
• type — various objects in the restrack database.
• user — user resource.
• id — ID to expose to users.

---

🦋 SEE ALSO 🦋

• Kernel file: ./include/rdma/restrack.h
• enum rdma_restrack_type(9)
• rdma_is_kernel_res(9)
• rdma_restrack_get(9)
• rdma_restrack_put(9)
• rdma_restrack_no_track(9)

---

mwah 💋 source/version: ./include/rdma, dated October 2026, and it’s the struct rdma_restrack_entry(9) page. byeee 🫶