rdtgroup_tasks_assigned(9)

💅 rdtgroup_tasks_assigned — the "is anyone actually in here??" check

okay so this is a page from the Kernel API Manual (section 9, bestie, kernel API territory), and it's about rdtgroup_tasks_assigned — literally the function that tells you whether any tasks have been assigned to a resource group. That's it. That's the whole vibe check. ✨

---

🌸 NAME 🌸

rdtgroup_tasks_assigned — Test if tasks have been assigned to resource group 🫶

like... it tests it. it's a test. that's the job. no cap.

---

🦋 SYNOPSIS 🦋

int rdtgroup_tasks_assigned (struct rdtgroup *r );

that's the whole signature, mwah 💋. returns an int, takes a struct rdtgroup * named r. clean, simple, iconic.

---

🎀 ARGUMENTS 🎀

• r — Resource group 💖 this is the resource group you're asking about. the one getting the vibe check. the main character, honestly.

---

⭐ RETURN ⭐

• 1 if tasks have been assigned to r
• 0 otherwise

so like, one means "yes bestie, there are tasks in there", zero means "it's empty, nobody home 😭". binary as hell and we love that for it.

---

🔥 SEE ALSO 🔥

the friend group!! go say hi 👑 all of these live in the kernel file ./fs/resctrl/rdtgroup.c:

• closid_allocated(9)
• rdtgroup_mode_by_closid(9)
• rdtgroup_mode_str(9)
• rdtgroup_remove(9)
• __rdtgroup_cbm_overlaps(9)
• rdtgroup_cbm_overlaps(9)
• rdtgroup_mode_test_exclusive(9)
• rdtgroup_cbm_to_size(9)
• rdtgroup_kn_mode_restrict(9)
• rdtgroup_kn_mode_restore(9)
• mon_get_kn_priv(9)
• mon_put_kn_priv(9)
• cbm_ensure_valid(9)
• mongrp_reparent(9)
• domain_setup_l3_mon_state(9)
• resctrl_exit(9)

iykyk 💀 these are all the sibling functions, the whole resctrl family reunion.

---

anyway, that's the page!! this one came out of ./fs/resctrl and it's dated October 2026 — so yeah, mark your calendars, bestie 🎀✨ go check your resource groups, and remember: 1 means tasks showed up, 0 means the group is a ghost town 💜🦋