Lines Matching full:users

7 DAMON provides below interfaces for different users.
12   Using this, users can use the DAMON’s major features in a human-friendly way.
19   want more optimized use of DAMON.  Using this, users can use DAMON’s major
31   so users should move to the :ref:`sysfs interface <sysfs_interface>`.
34   users can utilize every feature of DAMON most flexibly and efficiently by
49 For a short example, users can monitor the virtual address space of a given
215 can be covered.  However, users could want to set the initial monitoring region
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
241 For usual DAMON-based data access aware memory management optimizations, users
244 schemes from the user and applies those to the target memory regions.  Users
290 can cause severe overhead.  To avoid such overhead, users can limit time and
291 size quota for each scheme.  In detail, users can ask DAMON to try to use only
298 and age.  For personalized prioritization, users can set the weights for the
399   users should move to the :ref:`sysfs interface <sysfs_interface>`.
409 Users can get and set the ``sampling interval``, ``aggregation interval``,
427 monitoring targets.  Users can set the targets by writing relevant id values of
439 Users can also monitor the physical memory address space of the system by
457 processes can be covered.  However, users can want to limit the monitoring
459 file-mapped area.  Or, some users can know the initial access pattern of their
464 regions in case of physical memory monitoring.  Therefore, users should set the
467 In such cases, users can explicitly set the initial monitoring target regions
491 regions after one ``update interval``.  Therefore, users should set the
499 For usual DAMON-based data access aware memory management optimizations, users
504 Users can get and set the schemes by reading from and writing to ``schemes``
546 can cause severe overhead.  To avoid such overhead, users can limit time and
559 and age.  For personalized prioritization, users can set the weights for the
568 metrics like free memory ratio.  For such cases, users can specify watermarks