mm/damon/design.rst

241 To make such access pattern maintained period analysis easier, DAMON maintains
257 and applies it to monitoring operations-related data structures such as the
282 One straightforward approach for such schemes would be profile-guided
292 effective, and therefore widely be used.   However, implementing such schemes
298 To allow users to reduce such redundancy and inefficiencies by offloading the
301 level.  For such specifications, DAMON starts monitoring, finds regions having
355 region's characteristics.  Hence, DAMOS resets the age of regions when any such
389 resources.  Preventing such issues by tuning the access pattern could be
475 consume unnecessary system resources.  To avoid such consumption, the user would
476 need to manually monitor some metrics such as free memory ratio, and turn
479 DAMOS allows users to offload such works using three watermarks.  It allows the
500 more than the kernel, such as future access patterns or some special
505 To let users optimize DAMOS schemes with such special knowledge, DAMOS provides
548 other kernel components such as subsystems and modules building their data
561 provide any direct interface for the user space.  Such interfaces should be
563 itself implements such DAMON API user modules, which are supposed to be used
582 and reading from the files.  As a response to such I/O, DAMON user interface
587 rather than human beings' fingers.  Human users are recommended to use such
588 user space tools.  One such Python-written user space tool is available at
604 operations such as proactive reclamation or LRU lists balancing, the interfaces
610 To support such cases, yet more DAMON API user kernel modules that provide more