proc_pid_statm(5)

💖 proc_pid_statm(5) — the /proc/pid/statm glow-up 💖

okay bestie, quick vibe check: this page lives in the File Formats Manual section, and it's all about peeking at how much memory a process is using. no cap, it's short, it's iconic, let's go 🦋

---

✨ NAME ✨

/proc/pid/statm — memory usage information, aka the receipts on how many pages your process is holding 📄

---

🌸 DESCRIPTION 🌸

/proc/pid/statm

So you open this file and it gives you the tea about memory usage, and the tea is measured in pages. 🫖✨ It's one line, seven columns, and here's the decoder ring:

• size (1) — total program size. literally the same thing as VmSize in /proc/pid/status 💅
• resident (2) — resident set size. and bestie, it's inaccurate. same as VmRSS in /proc/pid/status
• shared (3) — the number of resident shared pages (i.e., backed by a file). also inaccurate. same as RssFile+RssShmem in /proc/pid/status
• text (4) — text (code) 👑
• lib (5) — library. unused since Linux 2.6; always 0 💀
• data (6) — data + stack 🍓
• dt (7) — dirty pages. unused since Linux 2.6; always 0 🙈

ngl, some of these values are inaccurate because of a kernel-internal scalability optimization. that's just how it is, no shade to the kernel 😭

If you genuinely need accurate values, use /proc/pid/smaps or /proc/pid/smaps_rollup instead. the catch? they're much slower 💀 but they give you accurate, detailed information, so it's giving quality over speed, fr fr ✨

---

🎀 SEE ALSO 🎀

• proc(5)
• proc_pid_status(5)

---

and that's the whole page, bestie, you ate it 🫶 if you're curious where this came from: it's from Linux man-pages 6.20, dated 2026-02-08. mwah, go read your memory stats responsibly 💖🌈⭐