PROBE::VM.KMALLOC_(3stap)

πŸ’– probe::vm.kmalloc_node β€” from the SystemTap Tapset Reference, Memory Tapset edition πŸŽ€

okay bestie, welcome to PROBE::VM.KMALLOC_(3stap), aka the page where we vibe-check the kernel's memory allocation moment ✨


✨ NAME ✨

probe::vm.kmalloc_node β€” fires when kmalloc_node is requested πŸ’…


🌸 SYNOPSIS 🌸

probe vm.kmalloc_node {}

like… that's it. that's the whole thing. iconic minimalism, no cap πŸ¦‹


🫢 VALUES 🫢

these are the lil goodies this probe hands you, bestie. every single one, in order, no skips πŸ’–

  • gfp_flag_name β€” the type of kmemory to allocate, but make it a string format ✨ (yes, as a string, we love a glow-up)
  • call_site β€” the address of the function that's calling this kmemory function πŸ“
  • bytes_req β€” the requested Bytes. the ask. the dream. 🌈
  • name β€” name of the probe point 🏷️
  • ptr β€” pointer to the kmemory that got allocated πŸ”₯
  • caller_function β€” the name of the caller function, i.e. who did this πŸ™ˆ
  • bytes_alloc β€” the allocated Bytes. what actually happened vs. what was requested, the classic πŸ’€
  • gfp_flags β€” the type of kmemory to allocate (raw flags edition) πŸŽ€

πŸ‘‘ SEE ALSO πŸ‘‘


and that's the whole page, bestie. slay. πŸ’œ

SystemTap Tapset Reference, Version September 2026 β€” ty for reading, ily, go allocate something responsibly πŸ«ΆπŸ’–

πŸ“¦ where this page comes from