Lines Matching full: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
106 The monitoring-related information including request specifications and results
132 ``contexts`` directory contains files for controlling the monitoring contexts
140 ``0`` to ``N-1``. Each directory represents each monitoring context. At the
151 DAMON supports multiple types of monitoring operations, including those for
153 available monitoring operations set on the currently running kernel by reading
162 differences between the operations sets in terms of the monitoring target
165 You can set and get what type of monitoring operations DAMON will use for the
172 Files for specifying attributes of the monitoring including required quality
173 and efficiency of the monitoring are in ``monitoring_attrs`` directory.
183 of DAMON's monitoring regions (``min`` and ``max``, respectively), which
184 controls the monitoring overhead, exist. You can set and get the values by
187 For more details about the intervals and monitoring regions range, please refer
195 to ``N-1``. Each directory represents each monitoring target.
212 When ``vaddr`` monitoring operations set is being used (``vaddr`` is written to
214 monitoring target regions so that entire memory mappings of target processes
215 can be covered. However, users could want to set the initial monitoring region
218 In contrast, DAMON do not automatically sets and updates the monitoring target
219 regions when ``fvaddr`` or ``paddr`` monitoring operations sets are being used
221 Therefore, users should set the monitoring target regions by themselves in the
224 For such cases, users can explicitly set the initial monitoring target regions
229 to ``N-1``. Each directory represents each initial monitoring target region.
235 can set and get the start and end addresses of the initial monitoring target
359 free memory rate of the system every 5 seconds, start the monitoring and paging
410 ``update interval``, and min/max number of monitoring target regions by
411 reading from and writing to the ``attrs`` file. To know about the monitoring
425 Some types of address spaces supports multiple monitoring target. For example,
426 the virtual memory address spaces monitoring can have multiple processes as the
427 monitoring targets. Users can set the targets by writing relevant id values of
429 ``target_ids`` file. In case of the virtual address spaces monitoring, the
430 values should be pids of the monitoring target processes. For example, below
431 commands set processes having pids 42 and 4242 as the monitoring targets and
441 space monitoring doesn't support multiple targets, reading the file will show a
449 Note that setting the target ids doesn't start the monitoring.
452 Initial Monitoring Target Regions
455 In case of the virtual address space monitoring, DAMON automatically sets and
456 updates the monitoring target regions so that entire memory mappings of target
457 processes can be covered. However, users can want to limit the monitoring
463 In contrast, DAMON do not automatically sets and updates the monitoring target
464 regions in case of physical memory monitoring. Therefore, users should set the
465 monitoring target regions by themselves.
467 In such cases, users can explicitly set the initial monitoring target regions
476 ``100-200`` as the initial monitoring target region of pid 42, which is the
489 Note that this sets the initial monitoring target regions only. In case of
490 virtual memory monitoring, DAMON will automatically updates the boundary of the
607 free memory rate of the system every 5 seconds, start the monitoring and paging
623 start the monitoring. You can start, stop, and check the current status of the
624 monitoring by writing to and reading from the ``monitor_on`` file. Writing
625 ``on`` to the file starts the monitoring of the targets with the attributes.
637 the monitoring is turned on. If you write to the files while DAMON is running,
641 Monitoring Thread PID
644 DAMON does requested monitoring with a kernel thread called ``kdamond``. You
646 monitoring is turned off, reading the file returns ``none``. ::
658 Using Multiple Monitoring Threads
661 One ``kdamond`` thread is created for each monitoring context. You can create
662 and remove monitoring contexts for multiple ``kdamond`` required use case using
689 Tracepoint for Monitoring Results
692 DAMON provides the monitoring results via a tracepoint,
693 ``damon:damon_aggregated``. While the monitoring is turned on, you could