mm/damon/design.rst

25 For data access monitoring and additional low level work, DAMON needs a set of
47 Core layer of DAMON is implemented as a framework, and exposes its application
77 mapping is not strictly required but could even incur a high overhead in some
88 to make a reasonable trade-off.  Below shows this in detail::
107 table having a mapping to the address.  In this way, the implementations find
133 The output of DAMON says what pages are how frequently accessed for a given
161 that assumed to have the same access frequencies into a region.  As long as the
162 assumption (pages in a region have the same access frequencies) is kept, only
197 access pattern of a region has maintained.  That could be used for good
217 abstracted monitoring target memory area only for each of a user-specified time
233     using THP for memory regions that are larger than 2 MiB and showing a high
253 works, DAMON provides a feature called Data Access Monitoring-based Operation
254 Schemes (DAMOS).  It lets users specify their desired schemes at a high
279 Applying an action to a region is considered as changing the region's
292 interest by setting minimum and maximum values of the three properties.  If a
303 the target access pattern is not properly tuned.  For example, if a huge memory
312 can use for applying the action, and/or a maximum bytes of memory regions that
313 the action can be applied within a user-specified time duration.
321 A mechanism for making a good decision under the quotas.  When the action
349 only under certain situations.  For example, when a sufficient amount of free
350 memory is guaranteed, running a scheme for proactive reclamation would only
375 have a list of latency-critical processes.
378 a feature called DAMOS filters.  The feature allows users to set an arbitrary
396 operations set.  If a memory region is filtered by a core layer-handled filter,
397 it is not counted as the scheme has tried to the region.  In contrast, if a
407 DAMON is a framework, so it does nothing by itself.  Instead, it only helps
418 Because the core of DAMON is a framework for kernel components, it doesn't
440 and reading from the files.  As a response to such I/O, DAMON user interface