css_rstat_push_children(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… css_rstat_push_children(9) β€” a Kernel API Manual moment πŸŽ€

okay bestie, this one's from the Kernel API Manual and it's lowkey a whole vibe ✨ it's css_rstat_push_children, and no cap it does exactly one thing but it does it well 🫢


✨ NAME ✨

css_rstat_push_children β€” push children css's into the given list πŸ’– (yes that's the whole name, she's not wordy, she's efficient πŸ‘‘)


🌸 SYNOPSIS 🌸

struct cgroup_subsys_state * css_rstat_push_children (struct
cgroup_subsys_state *head , struct cgroup_subsys_state *child , int cpu
);

like, that's the whole signature. struct in, struct out, three args, periodt πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • head β€” the current head of the list (which also = the subtree root, iykyk 🌈)
  • child β€” the first child of the root, aka where the walk starts πŸ‘Ά
  • cpu β€” the target cpu. the one we're doing all this for πŸ–₯️

⭐ RETURN ⭐

A new singly linked list of css's to be flushed. that's it, that's the tea β˜• she hands you back a whole list and you're like "slay" πŸ’€


πŸ’œ DESCRIPTION πŸ’œ

okay so here's the lore πŸ”₯ the function iteratively traverses down the css_rstat_cpu updated tree, level by level, and pushes all the parents first before their next-level children into a singly linked list. the connection goes through the rstat_flush_next pointer, and the list is built from the tail backward, like "pushing" css's into a stack πŸ₯ž (yes, literally a stack, she said what she said).

and literally the root? the caller pushes that one, not this function. not her job, not her problem πŸ™ˆ

fr fr remember: the root is pushed by the caller. don't come for this function about the root, she doesn't know her πŸ’€

🧚 SEE ALSO 🧚


that's the page bestie, go forth and push some children 🌸🫢

sign-off szn: this one lives under ./kernel/cgroup and it's dated October 2026 β€” iconic, timeless, we stan a stable release calendar πŸ‘‘πŸ’–

πŸ“¦ where this page comes from