dump_tasks(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… dump_tasks

okay so welcome to the Kernel API Manual, bestie β€” this is the page for dump_tasks(9), and it's lowkey iconic. 🫢

🌸 NAME 🌸

dump_tasks β€” dump current memory state of all system tasks. Periodt. πŸ’…

πŸ¦‹ SYNOPSIS πŸ¦‹

void dump_tasks (struct oom_control *oc );

It's void, bestie β€” no return value to catch. ✨

πŸŽ€ ARGUMENTS πŸŽ€

  • oc β€” pointer to struct oom_control. That's the one and only arg, and yes, it's a pointer. πŸŽ€

✨ DESCRIPTION ✨

Okay so dump_tasks dumps the current memory state of all eligible tasks. Like, it's giving full memory-state recap energy. πŸ’…

The vibe check has rules, though: tasks not in the same memcg, not in the same cpuset, or bound to a disjoint set of mempolicy nodes are not shown. No cap. 🫢

The state info it includes is: the task's pid, uid, tgid, vm size, rss, pgtables_bytes, swapents, oom_score_adj value, and name. Literally all of those deets. 🌟

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./mm/oom_kill.c β€” and the whole related lineup:


xoxo, sourced from ./mm, dated October 2026, and it's dump_tasks(9) β€” mwah πŸ’–βœ¨

πŸ“¦ where this page comes from