mm/damon/usage.rst

19   features by reading from and writing to special sysfs files.  Therefore,
32   writing kernel space DAMON application programs for you.  You can even extend
43 ``<sysfs>/kernel/mm/damon/``.  You can control DAMON by writing to and reading
114 file, ``nr_kdamonds``.  Writing a number (``N``) to the file creates the number
125 ``off`` if it is not running.  Writing ``on`` or ``off`` makes the kdamond be
126 in the state.  Writing ``commit`` to the ``state`` file makes kdamond reads the
127 user inputs in the sysfs files except ``state`` file again.  Writing
132 Writing ``update_schemes_tried_regions`` to ``state`` file updates the
134 DAMON-based operation scheme of the kdamond.  Writing
136 ``.../tried_regions/total_bytes`` files.  Writing
151 In the beginning, this directory has only one file, ``nr_contexts``.  Writing a
181 context by writing one of the keywords listed in ``avail_operations`` file and
197 writing to and reading from the files.
202 writing to and rading from the files.
210 In the beginning, this directory has only one file, ``nr_targets``.  Writing a
221 be a process.  You can specify the process to DAMON by writing the pid of the
242 as they want, by writing proper values to the files under this directory.
244 In the beginning, this directory has only one file, ``nr_regions``.  Writing a
253 region by writing to and reading from the files, respectively.
263 writing to files under this directory.
265 In the beginning, this directory has only one file, ``nr_schemes``.  Writing a
308 exist.  You can set and get the access pattern for the given scheme by writing
324 ``reset interval`` in milliseconds by writing the values to the three files,
333 in per-thousand unit by writing the values to the three files under the
345 get the five values by writing to the files, respectively.
361 In the beginning, this directory has only one file, ``nr_filters``.  Writing a
372 cgroup of the interest by writing the path of the memory cgroup from the
417 stats by writing a special keyword, ``update_schemes_stats`` to the relevant
437 Writing ``update_schemes_tried_bytes`` to the relevant ``kdamonds/<N>/state``
495 <https://github.com/awslabs/damo>`_ rather than manually reading and writing
522 reading from and writing to the ``attrs`` file.  To know about the monitoring
538 monitoring targets.  Users can set the targets by writing relevant id values of
551 writing a special keyword, "``paddr\n``" to the file.  Because physical address
579 as they want, by writing proper values to the ``init_regions`` file.  The input
612 <damon_design_damos>` by reading from and writing to ``schemes`` debugfs file.
618 You can disable schemes by simply writing an empty string to the file.
732 monitoring by writing to and reading from the ``monitor_on`` file.  Writing
734 Writing ``off`` to the file stops those.  DAMON also stops if every target
773 Writing the name of the new context to the ``mk_contexts`` file creates a