This is also posted to DAMON mailing list. After DAMON has upstreamed in 2021, I shared yearly retrospects for 2022 [1] and 2023 [2]. And somehow I forgot to do that for 2024 and 2025. Let me share the retrospect of 2024, before my memory goes away. Summary 2024 was a year that DAMON has been more publicly and widely adopted. AWS published their usage of DAMON as a VLDB paper....
This is also posted to DAMON mailing list. Hello, Last year around this time, I shared a humble retrospect of DAMON for 2022[1], which was effectively the first year it had after it was merged in the mainline. As one more year has passed, I’d like to share that again for the second year of DAMON, with some events and statistics of this year’s DAMON development that I was personally interested in....
DAMON exports data access pattern of the system and workload to the user space in multiple ways. Tracepoint is one such way DAMON is using to provide the full access pattern monitoring results in real time. DAMON user-space tool (damo) collects and visualizes the information in a handy and human-friendly way. For the collection, damo was internally using perf. On some environments including Android, perf is not available. This made use of DAMON on Android and similar platforms difficult....
A number of DAMON changes for Linux 6.19-rc1 has merged into the mainline as a part of MM pull reqeust for Linux 6.19-rc1, which was sent by Andrew Morton. To list the changes here again: mm/damon: allow DAMOS auto-tuned for per-memcg per-node memory usage (patches) mm/damon: fixes for address alignment issues in DAMON_LRU_SORT and DAMON_RECLAIM (patches) mm/damon: misc documentation fixups (patches) mm/damon: support pin-point targets removal (patches) mm/damon/tests: fix memory bugs in kunit tests (patches) mm/damon/tests: add more tests for online parameters commit (patches) mm/damon: misc cleanups (patches)
Updates after initial posting. 2026-09-05 update: The milestone 1 is nearly done, and the milestone 2 is started. 2026-05-25 update: A roadmap for a part of this project is posted 2026-02-18 update: LSF/MM/BPF topic for discussing the NUMA hinting faults reuse is posted. 2026-01-13 update: The RFC v3 has posted to the mailing list. Below is also sent as a mail to DAMON mailing list and relevant people. I’m working [1] on extending DAMON to monitor accesses that are made by specific CPUs, and/or for writes....
This post lists research papers and news articles citing DAMON in an interesting way rather than just simple name listing. The list is collected in a human sense from incomplete searching, so it is quite far from perfect. Please reach out to sj@kernel.org if you want updates on the list. Yet another way to get the list would be using the Google Scholar for DAMON author-published paper ciataions (1, 2)....
2025-12-08 update: The RFC v3 is posted. From the very early days of DAMON, there were attempts to extend it for cpus-aware monitoring and write-only monitoring. In 2022, Xin Hao proposed extending DAMON for NUMA access statistics. In 2022 and 2025, Pedro Demarchi Gomes proposed extending DAMON for writes-only monitoring. Those proposals are not yet upstreamed though. We continued similar DAMON extension discussions publicly and privately, with multiple parties, though....