mm/damon/design.rst

60 programming interface to all kernel space components such as subsystems and
217 To make such access pattern maintained period analysis easier, DAMON maintains
233 and applies it to monitoring operations-related data structures such as the
253 One straightforward approach for such schemes would be profile-guided
263 effective, and therefore widely be used.   However, implementing such schemes
269 To allow users to reduce such redundancy and inefficiencies by offloading the
272 level.  For such specifications, DAMON starts monitoring, finds regions having
324 resources.  Preventing such issues by tuning the access pattern could be
382 consume unnecessary system resources.  To avoid such consumption, the user would
383 need to manually monitor some metrics such as free memory ratio, and turn
386 DAMOS allows users to offload such works using three watermarks.  It allows the
403 more than the kernel, such as future access patterns or some special
408 To let users optimize DAMOS schemes with such special knowledge, DAMOS provides
439 other kernel components such as subsystems and modules building their data
450 provide any direct interface for the user space.  Such interfaces should be
452 itself implements such DAMON API user modules, which are supposed to be used
471 and reading from the files.  As a response to such I/O, DAMON user interface
476 rather than human beings' fingers.  Human users are recommended to use such
477 user space tools.  One such Python-written user space tool is available at
493 operations such as proactive reclamation or LRU lists balancing, the interfaces
499 To support such cases, yet more DAMON API user kernel modules that provide more