PROBE::VM.KMEM_CAC(3stap)

💖 NAME 💖

okay bestie, gather round, because probe::vm.kmem_cache_alloc_node is the probe that fires when kmem_cache_alloc_node is requested. that's it, that's the whole vibe. she's a memory tapset girlie from 3stap and she's here to spill the tea on your kernel allocations ✨

---

🦋 SYNOPSIS 🦋

probe vm.kmem_cache_alloc_node {}

literally that. no args, no drama, just a probe point waiting to pop off 🎀

---

🌸 VALUES 🌸

these are the little goodies she hands you inside the probe. every single one, no skips:

• gfp_flag_name — the type of kmemory to allocate, but make it a string. yes queen, string format 💅
• call_site — the address of the function that's calling this kmemory function. like, who sent this request? we found them 🔍
• name — the name of the probe point. hi bestie, what's your name 💖
• bytes_req — the requested Bytes. what you asked for, periodt
• ptr — pointer to the kmemory allocated. that's the actual location, no cap 📍
• caller_function — name of the caller function. the human-readable version of call_site, slay
• bytes_alloc — the allocated Bytes. what you actually got — and ngl, sometimes that's not the same as what you asked for 👀
• gfp_flags — the type of kmemory to allocate. the raw flags version of gfp_flag_name ✨

not me pointing out that bytes_req and bytes_alloc are two different things… iykyk. one is the ask, one is the reality 🫶

---

🎀 SEE ALSO 🎀

• tapset::memory(3stap) — go read the memory tapset bestie, it's giving family reunion 🌈

---

okay that's the whole page!! this icon of a manual comes courtesy of the SystemTap Tapset Reference, and she's stamped September 2026 👑 thanks for coming to my ted talk, go probe some memory, you're doing amazing sweetie 💜