mm/damon/usage.rst

76     │ │ │ │ │ │ │ :ref:`regions <sysfs_regions>`/nr_regions
147   action tried regions directory for each DAMON-based operation scheme of the
149   regions directory, please refer to
154   action tried regions directory for each DAMON-based operation scheme of the
193 Please refer to :ref:`regions sysfs directory <sysfs_regions>` for detailed
195 regions.
217 of DAMON's monitoring regions (``min`` and ``max``, respectively), which
221 For more details about the intervals and monitoring regions range, please refer
239 (``regions``) exist.
247 targets/<N>/regions
252 monitoring target regions so that entire memory mappings of target processes
257 regions when ``fvaddr`` or ``paddr`` monitoring operations sets are being used
259 Therefore, users should set the monitoring target regions by themselves in the
262 For such cases, users can explicitly set the initial monitoring target regions
271 regions/<N>/
359 for applying the ``action`` to memory regions of the ``access_pattern``, and to
360 apply the action to only up to ``bytes`` bytes of memory regions within the
458 Also, memory regions that are filtered out by ``addr`` or ``target`` filters
459 are not counted as the scheme has tried to those, while regions that filtered
462 :ref:`tried regions <sysfs_schemes_tried_regions>`.
469 DAMON counts the total number and bytes of regions that each scheme is tried to
470 be applied, the two numbers for the regions that each scheme is successfully
490 that reading it returns the total size of the scheme tried regions, and creates
528 limitation, page out memory regions having longer age first.  Also, check the
572 provides the monitoring results for regions that each DAMON-based Operation
594 seventh field (``nr_regions=X``) shows the total number of monitoring regions
640 ``update interval``, and min/max number of monitoring target regions by
682 Initial Monitoring Target Regions
686 updates the monitoring target regions so that entire memory mappings of target
690 workloads and therefore want to set optimal initial regions for the 'adaptive
691 regions adjustment'.
694 regions in case of physical memory monitoring.  Therefore, users should set the
695 monitoring target regions by themselves.
697 In such cases, users can explicitly set the initial monitoring target regions
705 starting from ``0``, and the regions should be passed in address order.  For
720 Note that this sets the initial monitoring target regions only.  In case of
722 regions after one ``update interval``.  Therefore, users should set the
748 Specifically, bytes for the size of regions (``min-size`` and ``max-size``),
751 regions (``min-age`` and ``max-age``) are specified.  Note that the ranges are
781 the action to memory regions of the ``target access pattern`` within the
783 ``<sz>`` bytes of memory regions within the ``<reset interval>``.  Setting both
817 It also counts the total number and bytes of regions that each scheme is tried
818 to be applied, the two numbers for the regions that each scheme is successfully
833 limitation, page out memory regions having longer age first.  Also, check the