|
|
Subscribe / Log in / New account

Memory-management short topics: page-table sharing and working sets

Memory-management short topics: page-table sharing and working sets

Posted Jan 11, 2023 18:47 UTC (Wed) by mmechri (subscriber, #95694)
Parent article: Memory-management short topics: page-table sharing and working sets

Does anyone know how the work to augment MGLRU for working-set estimation compares to the following approaches?

- Brendan Gregg's WSS tools [1]
- DAMON [2] [3]

[1] https://www.brendangregg.com/wss.html
[2] https://damonitor.github.io/test/result/visual/v24/index....
[3] https://sjp38.github.io/post/damon_profile_callstack_exam...


to post comments

Memory-management short topics: page-table sharing and working sets

Posted Jan 12, 2023 23:02 UTC (Thu) by Yuanchu (subscriber, #153443) [Link]

The working set work focuses on understanding the usage pattern of a workload, per page type and per NUMA node, with granularity in minutes. It should also have low enough overhead that it doesn't impact application performance by much (to be evaluated), and could be turned on for most latency tolerant workloads to aid proactive reclaim.

The parallel in Brendan Gregg's WSS would be idle page tracking, which tracks accesses by setting and checking the PG_idle bit. The benefit here is that MGLRU already does almost all of this during aging, and is less clunky than userspace writing to /sys/kernel/mm/page_idle/bitmap.

With DAMON, you can get a lot more, e.g. a heatmap, but there's additional work and tuning required to make use of it. The working set extensions are really about exposing information MGLRU already has.


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds