TAPSET::PROC_MEM(3stap)

💖 TAPSET::PROC_MEM — the proc_mem tapset, explained bestie to bestie 💖

okay so this is the 3stap manual page for tapset::proc_mem — yes, the section is literally called 3stap, that's the manual name, we love a naming convention. anyway. it's the SystemTap tapset that's all about how much memory your current application is using, plus some cute little helper functions so you can actually read those numbers without crying. let's get into it 💅

---

✨ NAME ✨

tapset::proc_mem — the systemtap proc_mem tapset 🫶

---

🌸 DESCRIPTION 🌸

So like. The process memory query and utility functions here hand you info about the memory usage of the current application. They cover the full size, the resident size, the shared size, and the code and data being used by the current process. That's the whole squad right there.

And then — because raw page counts are giving "cryptic little gremlin" energy — there are also utility functions that let you query the page size of the current architecture and build human readable string representations of bytes and pages. so you can actually show your friends. obsessed. 😭

---

🎀 the functions themselves 🎀

heads up bestie: the page lists a bunch of these twice. same name, same one-liner, same See-also. not me inventing options, that's just what's on the page. keeping it 100% intact fr fr. 💀

proc_mem_size

Total program virtual memory size, measured in pages.

See function::proc_mem_size(3stap) for details.

proc_mem_size

Total program virtual memory size, measured in pages.

See function::proc_mem_size(3stap) for details.

proc_mem_rss

Program resident set size, in pages. that's the stuff actually chillin' in RAM.

See function::proc_mem_rss(3stap) for details.

proc_mem_rss

Program resident set size, in pages.

See function::proc_mem_rss(3stap) for details.

proc_mem_shr

Program shared pages — the ones coming from shared mappings.

See function::proc_mem_shr(3stap) for details.

proc_mem_shr

Program shared pages — the ones coming from shared mappings.

See function::proc_mem_shr(3stap) for details.

proc_mem_txt

Program text (aka code) size, in pages. the actual instructions, iconic.

See function::proc_mem_txt(3stap) for details.

proc_mem_txt

Program text (aka code) size, in pages.

See function::proc_mem_txt(3stap) for details.

proc_mem_data

Program data size — that's data + stack — in pages.

See function::proc_mem_data(3stap) for details.

proc_mem_data

Program data size — that's data + stack — in pages.

See function::proc_mem_data(3stap) for details.

mem_page_size

How many bytes are in a page on this architecture. architecture-dependent bestie, don't assume.

See function::mem_page_size(3stap) for details.

bytes_to_string

Gives you a human readable string for whatever byte count you hand it. glow up for numbers ✨

See function::bytes_to_string(3stap) for details.

pages_to_string

Turns pages into a human readable string. same energy, different unit.

See function::pages_to_string(3stap) for details.

proc_mem_string

A human readable string of the whole process memory usage. the main character of the string-ifiers 👑

See function::proc_mem_string(3stap) for details.

proc_mem_string

A human readable string of the whole process memory usage.

See function::proc_mem_string(3stap) for details.

---

👑 SEE ALSO 👑

go read these too, they're all linked and they all ate:

• function::proc_mem_size(3stap)
• function::proc_mem_rss(3stap)
• function::proc_mem_shr(3stap)
• function::proc_mem_txt(3stap)
• function::proc_mem_data(3stap)
• function::mem_page_size(3stap)
• function::bytes_to_string(3stap)
• function::pages_to_string(3stap)
• function::proc_mem_string(3stap)
• stap(1)
• stapprobes(3stap)

---

and that's the whole page bestie, no notes, every single function accounted for 💜

this lil love letter came to you from the SystemTap Tapset Reference, dated September 2026 — that's the TAPSET::PROC_MEM(3stap) footer energy, periodt. go check your RSS and hydrate 🦋✨🌸