mm/damon/usage.rst

108 The monitoring-related information including request specifications and results
145 ``contexts`` directory contains files for controlling the monitoring contexts
153 ``0`` to ``N-1``.  Each directory represents each monitoring context.  At the
166 DAMON supports multiple types of monitoring operations, including those for
168 available monitoring operations set on the currently running kernel by reading
177 differences between the operations sets in terms of the monitoring target
180 You can set and get what type of monitoring operations DAMON will use for the
189 Files for specifying attributes of the monitoring including required quality
190 and efficiency of the monitoring are in ``monitoring_attrs`` directory.
200 of DAMON's monitoring regions (``min`` and ``max``, respectively), which
201 controls the monitoring overhead, exist.  You can set and get the values by
204 For more details about the intervals and monitoring regions range, please refer
212 to ``N-1``.  Each directory represents each monitoring target.
229 When ``vaddr`` monitoring operations set is being used (``vaddr`` is written to
231 monitoring target regions so that entire memory mappings of target processes
232 can be covered.  However, users could want to set the initial monitoring region
235 In contrast, DAMON do not automatically sets and updates the monitoring target
236 regions when ``fvaddr`` or ``paddr`` monitoring operations sets are being used
238 Therefore, users should set the monitoring target regions by themselves in the
241 For such cases, users can explicitly set the initial monitoring target regions
246 to ``N-1``.  Each directory represents each initial monitoring target region.
252 can set and get the start and end addresses of the initial monitoring target
370 open-ended interval), or ``target`` for specific DAMON monitoring target
375 ``addr_start`` and ``addr_end`` files, respectively.  For the DAMON monitoring
377 the DAMON context's monitoring targets list to ``target_idx`` file.  You can
446 and query-like efficient data access monitoring results retrievals.  For the
466 free memory rate of the system every 5 seconds, start the monitoring and paging
521 ``update interval``, and min/max number of monitoring target regions by
522 reading from and writing to the ``attrs`` file.  To know about the monitoring
536 Some types of address spaces supports multiple monitoring target.  For example,
537 the virtual memory address spaces monitoring can have multiple processes as the
538 monitoring targets.  Users can set the targets by writing relevant id values of
540 ``target_ids`` file.  In case of the virtual address spaces monitoring, the
541 values should be pids of the monitoring target processes.  For example, below
542 commands set processes having pids 42 and 4242 as the monitoring targets and
552 space monitoring doesn't support multiple targets, reading the file will show a
560 Note that setting the target ids doesn't start the monitoring.
566 In case of the virtual address space monitoring, DAMON automatically sets and
567 updates the monitoring target regions so that entire memory mappings of target
568 processes can be covered.  However, users can want to limit the monitoring
574 In contrast, DAMON do not automatically sets and updates the monitoring target
575 regions in case of physical memory monitoring.  Therefore, users should set the
576 monitoring target regions by themselves.
578 In such cases, users can explicitly set the initial monitoring target regions
588 ``100-200`` as the initial monitoring target region of pid 42, which is the
601 Note that this sets the initial monitoring target regions only.  In case of
602 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 Users can get the monitoring results via the :ref:`tried_regions
804 monitoring is turned on, you could record the tracepoint events and show