mm/damon/usage.rst

19   features by reading from and writing to special sysfs files.  Therefore,
43 ``<sysfs>/kernel/mm/damon/``.  You can control DAMON by writing to and reading
132 Reading ``state`` returns ``on`` if the kdamond is currently running, or
157 If the state is ``on``, reading ``pid`` shows the pid of the kdamond thread.
185 available monitoring operations set on the currently running kernel by reading
199 reading from the ``operations`` file.
214 writing to and reading from the files.
276 region by writing to and reading from the files, respectively.
287 <damon_design_damos>`).  Users can get and set the schemes by reading from and
341 to and reading from the ``min`` and ``max`` files under ``sz``,
474 The statistics can be retrieved by reading the files under ``stats`` directory
490 that reading it returns the total size of the scheme tried regions, and creates
517 ``nr_accesses``, and ``age``).  Reading the files will show the start and end
558 <https://github.com/awslabs/damo>`_ rather than manually reading and writing
641 reading from and writing to the ``attrs`` file.  To know about the monitoring
658 the targets to, and get the ids of the current targets by reading from the
671 space monitoring doesn't support multiple targets, reading the file will show a
731 <damon_design_damos>` by reading from and writing to ``schemes`` debugfs file.
732 Reading the file also shows the statistics of each scheme.  To the file, each
822 The statistics can be shown by reading the ``schemes`` file.  Reading the file
851 monitoring by writing to and reading from the ``monitor_on`` file.  Writing
872 can get the pid of the thread by reading the ``kdamond_pid`` file.  When the
873 monitoring is turned off, reading the file returns ``none``. ::