Lines Matching full:files

19   features by reading from and writing to special sysfs files.  Therefore,
21   reads/writes the sysfs files instead of you.  The `DAMON user space tool
42 creates multiple directories and files under its sysfs directory,
44 from the files under the directory.
56 Files Hierarchy
59 The files hierarchy of DAMON sysfs interface is shown below.  In the below
61 directory is having ``/`` suffix, and files in each directory are separated by
107 has one directory named ``admin``.  The directory contains the files for
116 Under the ``admin`` directory, one directory, ``kdamonds``, which has files for
129 In each kdamond directory, two files (``state`` and ``pid``) and one directory
139 - ``commit``: Read the user inputs in the sysfs files except ``state`` file
143 - ``update_schemes_stats``: Update the contents of stats files for each
152   files.
157   ``effective_bytes`` files for each DAMON-based operation scheme of the
162 ``contexts`` directory contains files for controlling the monitoring contexts
182 In each context directory, two files (``avail_operations`` and ``operations``)
204 Files for specifying attributes of the monitoring including required quality
209 Under ``intervals`` directory, three files for DAMON's sampling interval
212 writing to and reading from the files.
214 Under ``nr_regions`` directory, two files for the lower-bound and upper-bound
217 writing to and rading from the files.
255 as they want, by writing proper values to the files under this directory.
266 In each region directory, you will find two files (``start`` and ``end``).  You
268 region by writing to and reading from the files, respectively.
280 writing to files under this directory.
292 ``watermarks``, ``filters``, ``stats``, and ``tried_regions``) and three files
316 ``nr_accesses``, and ``age``) each having two files (``min`` and ``max``)
318 to and reading from the ``min`` and ``max`` files under ``sz``,
330 Under ``quotas`` directory, four files (``ms``, ``bytes``,
335 ``reset interval`` in milliseconds by writing the values to the three files,
352 Under ``weights`` directory, three files (``sz_permil``,
356 in per-thousand unit by writing the values to the three files under the
373 Each goal directory contains three files, namely ``target_metric``,
377 of the files.  Note that users should further write
389 Under the watermarks directory, five files (``metric``, ``interval_us``,
392 get the five values by writing to the files, respectively.
415 Each filter directory contains six files, namely ``type``, ``matcing``,
424 to ``addr_start`` and ``addr_end`` files, respectively.  For the DAMON
462 The statistics can be retrieved by reading the files under ``stats`` directory
464 ``qt_exceeds``), respectively.  The files are not updated in real time, so you
465 should ask DAMON sysfs interface to update the content of the files for the
480 directory contains files exposing detailed information about each of the memory
504 In each region directory, you will find four files (``start``, ``end``,
505 ``nr_accesses``, and ``age``).  Reading the files will show the start and end
547 the files as above.  Above is only for an example.
619 DAMON exports nine files, ``DEPRECATED``, ``attrs``, ``target_ids``,
843 Setting the files as described above doesn't incur effect unless you explicitly
857 Please note that you cannot write to the above-mentioned debugfs files while
858 the monitoring is turned on.  If you write to the files while DAMON is running,
884 the ``mk_contexts`` and ``rm_contexts`` files.
888 DAMON debugfs files for the context. ::
904 Note that ``mk_contexts``, ``rm_contexts``, and ``monitor_on_DEPRECATED`` files