Lines Matching refs:monitoring
14 virtual and physical address spaces monitoring. For more detail, please
24 supports both virtual and physical address spaces monitoring. Note that this
26 monitoring results. For detailed monitoring results, DAMON provides a
113 The monitoring-related information including request specifications and results
146 ``contexts`` directory contains files for controlling the monitoring contexts
154 ``0`` to ``N-1``. Each directory represents each monitoring context. At the
167 DAMON supports multiple types of monitoring operations, including those for
169 available monitoring operations set on the currently running kernel by reading
178 differences between the operations sets in terms of the monitoring target
181 You can set and get what type of monitoring operations DAMON will use for the
190 Files for specifying attributes of the monitoring including required quality
191 and efficiency of the monitoring are in ``monitoring_attrs`` directory.
201 of DAMON's monitoring regions (``min`` and ``max``, respectively), which
202 controls the monitoring overhead, exist. You can set and get the values by
205 For more details about the intervals and monitoring regions range, please refer
213 to ``N-1``. Each directory represents each monitoring target.
230 When ``vaddr`` monitoring operations set is being used (``vaddr`` is written to
232 monitoring target regions so that entire memory mappings of target processes
233 can be covered. However, users could want to set the initial monitoring region
236 In contrast, DAMON do not automatically sets and updates the monitoring target
237 regions when ``fvaddr`` or ``paddr`` monitoring operations sets are being used
239 Therefore, users should set the monitoring target regions by themselves in the
242 For such cases, users can explicitly set the initial monitoring target regions
247 to ``N-1``. Each directory represents each initial monitoring target region.
253 can set and get the start and end addresses of the initial monitoring target
373 pattern of the scheme and/or the monitoring regions for the purpose, but that
458 free memory rate of the system every 5 seconds, start the monitoring and paging
513 ``update interval``, and min/max number of monitoring target regions by
514 reading from and writing to the ``attrs`` file. To know about the monitoring
528 Some types of address spaces supports multiple monitoring target. For example,
529 the virtual memory address spaces monitoring can have multiple processes as the
530 monitoring targets. Users can set the targets by writing relevant id values of
532 ``target_ids`` file. In case of the virtual address spaces monitoring, the
533 values should be pids of the monitoring target processes. For example, below
534 commands set processes having pids 42 and 4242 as the monitoring targets and
544 space monitoring doesn't support multiple targets, reading the file will show a
552 Note that setting the target ids doesn't start the monitoring.
558 In case of the virtual address space monitoring, DAMON automatically sets and
559 updates the monitoring target regions so that entire memory mappings of target
560 processes can be covered. However, users can want to limit the monitoring
566 In contrast, DAMON do not automatically sets and updates the monitoring target
567 regions in case of physical memory monitoring. Therefore, users should set the
568 monitoring target regions by themselves.
570 In such cases, users can explicitly set the initial monitoring target regions
580 ``100-200`` as the initial monitoring target region of pid 42, which is the
593 Note that this sets the initial monitoring target regions only. In case of
594 virtual memory monitoring, DAMON will automatically updates the boundary of the
715 free memory rate of the system every 5 seconds, start the monitoring and paging
731 start the monitoring. You can start, stop, and check the current status of the
732 monitoring by writing to and reading from the ``monitor_on`` file. Writing
733 ``on`` to the file starts the monitoring of the targets with the attributes.
745 the monitoring is turned on. If you write to the files while DAMON is running,
752 DAMON does requested monitoring with a kernel thread called ``kdamond``. You
754 monitoring is turned off, reading the file returns ``none``. ::
769 One ``kdamond`` thread is created for each monitoring context. You can create
770 and remove monitoring contexts for multiple ``kdamond`` required use case using
800 DAMON provides the monitoring results via a tracepoint,
801 ``damon:damon_aggregated``. While the monitoring is turned on, you could