rdmacg_uncharge(9)
π 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 tocgto 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:
uncharge_cg_locked(9)rdmacg_event_locked(9)rdmacg_uncharge_hierarchy(9)rdmacg_try_charge(9)rdmacg_register_device(9)rdmacg_unregister_device(9)rdmacg_css_offline(9)
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms