mm/damon/usage.rst

184 virtual address space and the physical address space.  You can get the list of
197 You can set and get what type of monitoring operations DAMON will use for the
213 (``update_us``) exist.  You can set and get the values in micro-seconds by
218 controls the monitoring overhead, exist.  You can set and get the values by
275 can set and get the start and end addresses of the initial monitoring target
287 <damon_design_damos>`).  Users can get and set the schemes by reading from and
340 exist.  You can set and get the access pattern for the given scheme by writing
386 ``current_value``.  Users can set and get any number to those files to set the
404 get the five values by writing to the files, respectively.
430 ``memcg`` for specific memory cgroup, ``addr`` for specific address range (an
458 Also, memory regions that are filtered out by ``addr`` or ``target`` filters
566 Users can get the monitoring results via the :ref:`tried_regions
631 DAMON exports eight files, ``attrs``, ``target_ids``, ``init_regions``,
639 Users can get and set the ``sampling interval``, ``aggregation interval``,
641 reading from and writing to the ``attrs`` file.  To know about the monitoring
647     # echo 5000 100000 1000000 10 1000 > attrs
648     # cat attrs
658 the targets to, and get the ids of the current targets by reading from the
730 Users can get and set the DAMON-based operation :ref:`schemes
872 can get the pid of the thread by reading the ``kdamond_pid`` file.  When the
901     # attrs  init_regions  kdamond_pid  schemes  target_ids