Lines Matching full:regions

88 and updates the monitoring target address regions so that entire memory
97 address regions is just wasteful.  However, because DAMON can deal with some
98 level of noise using the adaptive regions adjustment mechanism, tracking every
104 distinct regions that cover every mapped area of the address space.  The two
105 gaps between the three regions are the two biggest unmapped areas in the given
115     (small mmap()-ed regions and munmap()-ed regions)
151 ``update interval``, ``minimum number of regions``, and ``maximum number of
152 regions``.
199 controllable by setting the number of regions.  DAMON allows users to set the
200 minimum and the maximum number of regions for the trade-off.
208 Adaptive Regions Adjustment
211 Even somehow the initial monitoring target regions are well constructed to
218 (``nr_accesses``) of adjacent regions.  If the difference is small, and if the
219 sum of the two regions' sizes is smaller than the size of total regions divided
220 by the ``minimum number of regions``, DAMON merges the two regions.  If the
221 resulting number of total regions is still higher than ``maximum number of
222 regions``, it repeats the merging with increasing access frequenceis difference
223 threshold until the upper-limit of the number of regions is met, or the
227 three regions if the total number of regions will not exceed the user-specified
228 maximum number of regions after the split.
265 :ref:`DAMOS tried regions <sysfs_schemes_tried_regions>` and :ref:`tracepoint`,
276 and ``age`` of regions in the aggregated monitoring results snapshot.  The
286 to converge regions with the :ref:`regions adjustment mechanism
294 monitoring results show zero ``nr_accesses``, regions could still be
307 accessed, or samely frequently accessed.  That is, regions become
332     paging out memory regions that are not accessed for more than two minutes
336     using THP for memory regions that are larger than 2 MiB and showing a high
341 workloads or the system using DAMON, finding memory regions of special
343 operation changes for the regions.  The changes could be made by modifying or
358 level.  For such specifications, DAMON starts monitoring, finds regions having
360 to the regions, for every user-specified time interval called
373 The management action that the users desire to apply to the regions of their
376 collecting statistics of the regions.
404  - ``migrate_hot``: Migrate the regions prioritizing warmer regions.
406  - ``migrate_cold``: Migrate the regions prioritizing colder regions.
412 region's characteristics.  Hence, DAMOS resets the age of regions when any such
430 regions that the scheme is having an interest in.
452 can use for applying the action, and/or a maximum bytes of memory regions that
466 cannot be applied to all regions of interest due to the quotas, DAMOS
467 prioritizes regions and applies the action to only regions having high enough
471 rarely accessed (colder) memory regions would be prioritized for page-out
472 scheme action.  In contrast, the colder regions would be deprioritized for huge
477 to calculate the priority using the access pattern properties of the regions.
555 Non-access pattern-based target memory regions filtering.  If users run
596 case of the core layer-handled filters, the memory regions that excluded by the
598 a memory regions is filtered by an operations set layer-handled filter, it is
635 - ``nr_tried``: Total number of regions that the scheme is tried to be applied.
636 - ``sz_trtied``: Total size of regions that the scheme is tried to be applied.
639 - ``nr_applied``: Total number of regions that the scheme is applied.
640 - ``sz_applied``: Total size of regions that the scheme is applied.
667 Regions Walking
672 access full properties of the regions including the access monitoring results