Lines Matching refs:each

63 figure, parents-children relations are represented with indentations, each
64 directory is having ``/`` suffix, and files in each directory are separated by
107 are called DAMON context.  DAMON executes each context with a kernel thread
113 of child directories named ``0`` to ``N-1``.  Each directory represents each
119 In each kdamond directory, two files (``state`` and ``pid``) and one directory
127 for each DAMON-based operation scheme of the kdamond.  For details of the
140 ``0`` to ``N-1``.  Each directory represents each monitoring context.  At the
147 In each context directory, two files (``avail_operations`` and ``operations``)
195 to ``N-1``.  Each directory represents each monitoring target.
200 In each target directory, one file (``pid_target``) and one directory
203 If you wrote ``vaddr`` to the ``contexts/<N>/operations``, each target should
229 to ``N-1``.  Each directory represents each initial monitoring target region.
234 In each region directory, you will find two files (``start`` and ``end``).  You
250 to ``N-1``.  Each directory represents each DAMON-based operation scheme.
255 In each scheme directory, four directories (``access_pattern``, ``quotas``,
274 The target access pattern of each DAMON-based operation scheme is constructed
280 ``nr_accesses``, and ``age``) each having two files (``min`` and ``max``)
288 Optimal ``target access pattern`` for each ``action`` is workload dependent, so
291 size quota for each scheme.  In detail, users can ask DAMON to try to use only
314 To allow easy activation and deactivation of each scheme based on system
323 ``high``, ``mid``, and ``low``) for setting each value exist.  You can set and
339 DAMON counts the total number and bytes of regions that each scheme is tried to
340 be applied, the two numbers for the regions that each scheme is successfully
505 debugfs file.  Reading the file also shows the statistics of each scheme.  To
506 the file, each of the schemes should be represented in each line in below
544 Optimal ``target access pattern`` for each ``action`` is workload dependent, so
590 It also counts the total number and bytes of regions that each scheme is tried
591 to be applied, the two numbers for the regions that each scheme is successfully
596 will show each scheme you entered in each line, and the five numbers for the
597 statistics will be added at the end of each line.
661 One ``kdamond`` thread is created for each monitoring context.  You can create