rdmacg_uncharge(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… rdmacg_uncharge β€” the kernel API manual, bestie edition

Okay so real talk, this whole page is about rdmacg_uncharge, which is a function from the Kernel API Manual. Yes, that Kernel API Manual. Pull up a chair πŸŽ€


✨ NAME ✨

rdmacg_uncharge β€” hier<a>chically uncharge rdma resource count

Not me being the one who gives back the RDMA resources πŸ’€ it's literally the inverse of charging, and she does it hierarchically, up the whole family tree.

🌸 SYNOPSIS 🌸

void rdmacg_uncharge (struct rdma_cgroup *cg , struct rdmacg_device
*device , enum rdmacg_resource_type index );

Notice it returns void? She gives nothing back on the return-value front. She's just out here uncharging. Periodt. ✨


πŸ¦‹ ARGUMENTS πŸ¦‹

  • cg β€” pointer to cg to uncharge and all parents in hierarchy πŸ‘‘ this is a whole family situation, not a solo mission. Every ancestor gets visited too.
  • device β€” pointer to the rdmacg device. That's the device bestie, what else.
  • index β€” index of the resource to uncharge in the cgroup in the given resource pool. Like, which resource, specifically, from which pool. Precision queen πŸ’…

πŸ‘‘ SEE ALSO πŸ‘‘

The kernel file ./kernel/cgroup/rdma.c and its friends β€” literally the whole squad, no cap:


Fr fr, if you're poking around in here you probably also want the charging side of the story (rdmacg_try_charge(9)), because what is uncharging without charging 😭 they're a matched set, iykyk.

And that's the vibe check 🧚 This icon of a page lives under ./kernel/cgroup, dated October 2026, and yes she's still rdmacg_uncharge(9) β€” mwah, slay, go read the source bestie πŸŒˆπŸ’–

πŸ“¦ where this page comes from