Lines Matching full:regions

74     │ │ │ │ │ │ │ regions/nr_regions
133 DAMON-based operation scheme action tried regions directory for each
138 operating scheme action tried regions directory for each DAMON-based operation
140 tried regions directory, please refer to :ref:`tried_regions section
176 Please refer to :ref:`regions sysfs directory <sysfs_regions>` for detailed
178 regions.
200 of DAMON's monitoring regions (``min`` and ``max``, respectively), which
204 For more details about the intervals and monitoring regions range, please refer
218 (``regions``) exist.
226 targets/<N>/regions
231 monitoring target regions so that entire memory mappings of target processes
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
248 regions/<N>/
326 for applying the ``action`` to memory regions of the ``access_pattern``, and to
327 apply the action to only up to ``bytes`` bytes of memory regions within the
397 Also, memory regions that are filtered out by ``addr`` or ``target`` filters
398 are not counted as the scheme has tried to those, while regions that filtered
401 :ref:`tried regions <sysfs_schemes_tried_regions>`.
408 DAMON counts the total number and bytes of regions that each scheme is tried to
409 be applied, the two numbers for the regions that each scheme is successfully
429 that reading it returns the total size of the scheme tried regions, and creates
465 limitation, page out memory regions having longer age first.  Also, check the
521 ``update interval``, and min/max number of monitoring target regions by
563 Initial Monitoring Target Regions
567 updates the monitoring target regions so that entire memory mappings of target
571 workloads and therefore want to set optimal initial regions for the 'adaptive
572 regions adjustment'.
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
586 starting from ``0``, and the regions should be passed in address order.  For
601 Note that this sets the initial monitoring target regions only.  In case of
603 regions after one ``update interval``.  Therefore, users should set the
629 Specifically, bytes for the size of regions (``min-size`` and ``max-size``),
632 regions (``min-age`` and ``max-age``) are specified.  Note that the ranges are
662 the action to memory regions of the ``target access pattern`` within the
664 ``<sz>`` bytes of memory regions within the ``<reset interval>``.  Setting both
698 It also counts the total number and bytes of regions that each scheme is tried
699 to be applied, the two numbers for the regions that each scheme is successfully
714 limitation, page out memory regions having longer age first.  Also, check the
802 While the tried regions directory is useful for getting a snapshot, the