Lines Matching full:monitoring
13 The monitoring-related information including the monitoring request
17 types of monitoring.
26 the given monitoring target address-space and available set of
28 - Core: Implements core logics including monitoring overhead/accurach control
37 For data access monitoring and additional low level work, DAMON needs a set of
69 The monitoring operations are defined in two parts:
71 1. Identification of the monitoring target address range for the address space.
81 This is only for the virtual address space monitoring operations
83 manually set the monitoring target address ranges.
90 cases. That said, too huge unmapped areas inside the monitoring target should
133 Monitoring section in Core Logics
137 monitoring attributes, ``sampling interval``, ``aggregation interval``,
142 Access Frequency Monitoring argument
165 The monitoring overhead of this mechanism will arbitrarily increase as the
181 called ``nr_regions`` of the region. Therefore, the monitoring overhead is
192 Even somehow the initial monitoring target regions are well constructed to
195 monitoring quality. To keep the assumption as much as possible, DAMON
213 By analyzing the monitoring results, users can also find how long the current
227 The monitoring target address range could dynamically changed. For example,
232 monitoring operations to check dynamic changes including memory mapping changes
233 and applies it to monitoring operations-related data structures such as the
234 abstracted monitoring target memory area only for each of a user-specified time
243 One common purpose of data access monitoring is access-aware system efficiency
254 optimizations. That is, getting data access monitoring results of the
256 characteristics by profiling the monitoring results, and making system
266 including monitoring results and operation advice between kernel and user
270 works, DAMON provides a feature called Data Access Monitoring-based Operation
272 level. For such specifications, DAMON starts monitoring, finds regions having
290 normally depends on the monitoring target address space. For example, the code
292 physical address ranges. And the monitoring operations implementation sets are
308 the properties that DAMON's monitoring results provide, specifically the size,
391 is activated. If all schemes are deactivated by the watermarks, the monitoring
414 Currently, anonymous page, memory cgroup, address range, and DAMON monitoring
418 type asks the start and end addresses of the range. The DAMON monitoring
419 target type asks the index of the target from the context's monitoring targets
423 monitoring targets, and any combination of those.
425 To handle filters efficiently, the address range and DAMON monitoring target