Lines Matching full:reading

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
124 Reading ``state`` returns ``on`` if the kdamond is currently running, or
143 If the state is ``on``, reading ``pid`` shows the pid of the kdamond thread.
168 available monitoring operations set on the currently running kernel by reading
182 reading from the ``operations`` file.
197 writing to and reading from the files.
253 region by writing to and reading from the files, respectively.
262 <damon_design_damos>`).  Users can get and set the schemes by reading from and
309 to and reading from the ``min`` and ``max`` files under ``sz``,
413 The statistics can be retrieved by reading the files under ``stats`` directory
429 that reading it returns the total size of the scheme tried regions, and creates
454 ``nr_accesses``, and ``age``).  Reading the files will show the start and end
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
539 the targets to, and get the ids of the current targets by reading from the
552 space monitoring doesn't support multiple targets, reading the file will show a
612 <damon_design_damos>` by reading from and writing to ``schemes`` debugfs file.
613 Reading the file also shows the statistics of each scheme.  To the file, each
703 The statistics can be shown by reading the ``schemes`` file.  Reading the file
732 monitoring by writing to and reading from the ``monitor_on`` file.  Writing
753 can get the pid of the thread by reading the ``kdamond_pid`` file.  When the
754 monitoring is turned off, reading the file returns ``none``. ::