rdma_restrack_begin_del(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… rdma_restrack_begin_del πŸ’…

okay so we're in the Kernel API Manual, bestie β€” welcome to the resource-tracking corner of the kernel, it's giving very backstage-pass energy πŸŽ€


✨ NAME ✨

rdma_restrack_begin_del β€” invalidates the object from the resource tracking database, but preserves its index in the array πŸ’– lowkey the whole personality of this function is "you're dead to me but you keep your seat".

And here's the part you actually need to know, no cap: since this keeps the index in the array until rdma_restrack_commit_del() gets called, if rdma_restrack_add() is called in between with an old QP ID, it can result in an untracked QP πŸ˜­πŸ™ˆ like. that's the trap. that's the vibe check failing.


🌸 SYNOPSIS 🌸

void rdma_restrack_begin_del (struct rdma_restrack_entry *res );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • res β€” resource entry πŸ‘‘ (that's the struct of the thing you're starting to delete, mwah)

⭐ SEE ALSO ⭐

Kernel file ./drivers/infiniband/core/restrack.c β€” go read it, iykyk πŸ“–βœ¨ and while you're at it, the whole friend group:


πŸ’€ reminder for the girlies: begin_del is not the whole delete. it's the beginning. don't be out here acting like the index is free when it literally is not 🫢

that's the whole page, bestie β€” brought to you straight outta ./drivers/infiniband/core, dated October 2026, in all its Kernel API Manual glory πŸŒˆπŸ’œ slay, go track some resources responsibly πŸ’…

πŸ“¦ where this page comes from