13 The monitoring-related information including the monitoring request
17 types of monitoring.
29   operations for DAMON that depends on the given monitoring target
31 - :ref:`Core <damon_core_logic>`: Implements core logics including monitoring
46 For data access monitoring and additional low level work, DAMON needs a set of
49 monitoring are address-space dependent.
51 1. Identification of the monitoring target address range for the address space.
57 monitoring accruracy and the overhead.
88 and updates the monitoring target address regions so that entire memory
93 monitoring target address ranges.
100 cases.  That said, too huge unmapped areas inside the monitoring target should
146 Monitoring  section in Core Logics
150 monitoring attributes, ``sampling interval``, ``aggregation interval``,
159 Access Frequency Monitoring  argument
182 The monitoring overhead of this mechanism will arbitrarily increase as the
198 called ``nr_accesses`` of the region.  Therefore, the monitoring overhead is
211 Even somehow the initial monitoring target regions are well constructed to
214 monitoring quality.  To keep the assumption as much as possible, DAMON
239 By analyzing the monitoring results, users can also find how long the current
253 The monitoring target address range could dynamically changed.  For example,
258 monitoring operations to check dynamic changes including memory mapping changes
259 and applies it to monitoring operations-related data structures such as the
260 abstracted monitoring target memory area only for each of a user-specified time
263 User-space can get the monitoring results via DAMON sysfs interface and/or
271 Monitoring Parameters Tuning Guide  argument
276 and ``age`` of regions in the aggregated monitoring results snapshot.  The
282 can make an amount of accesses for the monitoring purpose, within the interval.
284 result, the monitoring results look everything is samely accessed only rarely.
290 monitoring purpose too high.  For such cases, the target amount of access to
294 monitoring results show zero ``nr_accesses``, regions could still be
299 amount of access that captured on each aggregated snapshot of the monitoring
306 too large, monitoring results will look like every region was samely rarely
310 degrade the resolution, but will increase the monitoring overhead.  If it is
311 appropriate enough to provide a resolution of the monitoring results that
329 One common purpose of data access monitoring is access-aware system efficiency
340 optimizations.  That is, getting data access monitoring results of the
342 characteristics by profiling the monitoring results, and making system
352 including monitoring results and operation advice between kernel and user
356 works, DAMON provides a feature called Data Access Monitoring-based Operation
358 level.  For such specifications, DAMON starts monitoring, finds regions having
380 normally depends on the monitoring target address space.  For example, the code
382 physical address ranges.  And the monitoring operations implementation sets are
426 the properties that DAMON's monitoring results provide, specifically the size,
541 is activated.  If all schemes are deactivated by the watermarks, the monitoring
616 - DAMON monitoring target
617     - Applied to pages that belonging to a given DAMON monitoring target.
629 The statistics of DAMOS behaviors that designed to help monitoring, tuning and
672 access full properties of the regions including the access monitoring results