Improving page_owner for profiling and monitoring memory usage per all...
summary
page_owner now records allocation stack handles (not just text) via a new show_handles file so userspace can sample stack IDs cheaply, then resolve them once with show_stacks_handles, cutting repeated hashing overhead; example run shows dd 256MB -> 65,536 pages and samples match. swap support stores the original allocation trace at swap-out and restores it at swap-in, exposed via swap_page_owner, so swapped pages remain attributable to their allocators. patches merged for 6.19; runtime overhead still unmeasured.
AI-written summary · about
chapters (7)
- 0:00Introduction to page_owner
- 2:06What is page_owner
- 4:12Profiling and monitoring with page_owner
- 6:43Improving output format efficiency
- 9:10Adding swap space support
- 13:04Before and after swap support
- 14:30Q&A and discussion
related talks
32mIs Your Kernel Being Honest? Understanding & measuring low level bottlenecks
33mMemory Profiling for Mere Mortals
37mAdvanced Performance Profiling Using Perf Tools
31mProfiling Formats and Why You Should Care
01h 02mObject Introspection: A C++ Memory Profiler
27mWhen Linux Memory Accounting Goes Wrong
14mIchnaea: A Framework for Precise Tracking of Memory Objects
26mProfiling Mastery: Decode Your Data and Elevate Observability