Lines Matching +full:directory +full:- +full:based
1 .. SPDX-License-Identifier: GPL-2.0
9 - *DAMON user space tool.*
11 system administrators who want a just-working human-friendly interface.
12 Using this, users can use the DAMON’s major features in a human-friendly way.
16 - *sysfs interface.*
23 - *Kernel Space Programming Interface.*
36 creates multiple directories and files under its sysfs directory,
38 from the files under the directory.
51 ---------------
54 figure, parents-children relations are represented with indentations, each
55 directory is having ``/`` suffix, and files in each directory are separated by
58 .. parsed-literal::
98 ----
101 has one directory named ``admin``. The directory contains the files for
103 having the root permission could use this directory.
108 ---------
110 Under the ``admin`` directory, one directory, ``kdamonds``, which has files for
113 details) exists. In the beginning, this directory has only one file,
115 child directories named ``0`` to ``N-1``. Each directory represents each
121 -------------
123 In each kdamond directory, two files (``state`` and ``pid``) and one directory
131 - ``on``: Start running.
132 - ``off``: Stop running.
133 - ``commit``: Read the user inputs in the sysfs files except ``state`` file
135 - ``commit_schemes_quota_goals``: Read the DAMON-based operation schemes'
137 - ``update_schemes_stats``: Update the contents of stats files for each
138 DAMON-based operation scheme of the kdamond. For details of the stats,
140 - ``update_schemes_tried_regions``: Update the DAMON-based operation scheme
141 action tried regions directory for each DAMON-based operation scheme of the
142 kdamond. For details of the DAMON-based operation scheme action tried
143 regions directory, please refer to
145 - ``update_schemes_tried_bytes``: Update only ``.../tried_regions/total_bytes``
147 - ``clear_schemes_tried_regions``: Clear the DAMON-based operating scheme
148 action tried regions directory for each DAMON-based operation scheme of the
150 - ``update_schemes_effective_quotas``: Update the contents of
151 ``effective_bytes`` files for each DAMON-based operation scheme of the
152 kdamond. For more details, refer to :ref:`quotas directory <sysfs_quotas>`.
156 ``contexts`` directory contains files for controlling the monitoring contexts
162 ----------------------
164 In the beginning, this directory has only one file, ``nr_contexts``. Writing a
166 ``0`` to ``N-1``. Each directory represents each monitoring context (refer to
174 -------------
176 In each context directory, two files (``avail_operations`` and ``operations``)
184 ``avail_operations`` file. Based on the kernel configuration, the file will
196 ------------------------------
199 and efficiency of the monitoring are in ``monitoring_attrs`` directory.
201 directory.
203 Under ``intervals`` directory, three files for DAMON's sampling interval
205 (``update_us``) exist. You can set and get the values in micro-seconds by
208 Under ``nr_regions`` directory, two files for the lower-bound and upper-bound
219 ---------------------
221 In the beginning, this directory has only one file, ``nr_targets``. Writing a
223 to ``N-1``. Each directory represents each monitoring target.
228 ------------
230 In each target directory, one file (``pid_target``) and one directory
240 -------------------
249 as they want, by writing proper values to the files under this directory.
251 In the beginning, this directory has only one file, ``nr_regions``. Writing a
253 to ``N-1``. Each directory represents each initial monitoring target region.
258 ------------
260 In each region directory, you will find two files (``start`` and ``end``). You
264 Each region should not overlap with others. ``end`` of directory ``N`` should
265 be equal or smaller than ``start`` of directory ``N+1``.
270 ---------------------
272 The directory for DAMON-based Operation Schemes (:ref:`DAMOS
274 writing to files under this directory.
276 In the beginning, this directory has only one file, ``nr_schemes``. Writing a
278 to ``N-1``. Each directory represents each DAMON-based operation scheme.
283 ------------
285 In each scheme directory, five directories (``access_pattern``, ``quotas``,
304 ---------------------------
306 The directory for the target access :ref:`pattern
307 <damon_design_damos_access_pattern>` of the given DAMON-based operation scheme.
309 Under the ``access_pattern`` directory, three directories (``sz``,
319 -------------------
321 The directory for the :ref:`quotas <damon_design_damos_quotas>` of the given
322 DAMON-based operation scheme.
324 Under ``quotas`` directory, four files (``ms``, ``bytes``,
338 transformed size quota and user-specified size quota, smaller one is applied.
339 Based on the user-specified :ref:`goal <sysfs_schemes_quota_goals>`, the
346 Under ``weights`` directory, three files (``sz_permil``,
350 in per-thousand unit by writing the values to the three files under the
351 ``weights`` directory.
356 -------------------------
358 The directory for the :ref:`automatic quota tuning goals
359 <damon_design_damos_quotas_auto_tuning>` of the given DAMON-based operation
362 In the beginning, this directory has only one file, ``nr_goals``. Writing a
364 to ``N-1``. Each directory represents each goal and current achievement.
367 Each goal directory contains three files, namely ``target_metric``,
369 parameters for the quota auto-tuning goals that specified on the :ref:`design
373 directory <sysfs_kdamond>` to pass the feedback to DAMON.
378 -----------------------
380 The directory for the :ref:`watermarks <damon_design_damos_watermarks>` of the
381 given DAMON-based operation scheme.
383 Under the watermarks directory, five files (``metric``, ``interval_us``,
391 - none: Ignore the watermarks
392 - free_mem_rate: System's free memory rate (per thousand)
399 --------------------
401 The directory for the :ref:`filters <damon_design_damos_filters>` of the given
402 DAMON-based operation scheme.
404 In the beginning, this directory has only one file, ``nr_filters``. Writing a
406 to ``N-1``. Each directory represents each filter. The filters are evaluated
409 Each filter directory contains seven files, namely ``type``, ``matching``,
413 pages, ``addr`` for specific address range (an open-ended interval), or
431 For example, below restricts a DAMOS action to be applied to only non-anonymous
453 ------------------
459 The statistics can be retrieved by reading the files under ``stats`` directory
469 --------------------------
471 This directory initially has one file, ``total_bytes``.
476 directories named integer starting from ``0`` under this directory. Each
477 directory contains files exposing detailed information about each of the memory
479 this directory, during next :ref:`apply interval <damon_design_damos>` of the
491 The expected usage of this directory is investigations of schemes' behaviors,
492 and query-like efficient data access monitoring results retrievals. For the
499 ------------------
501 In each region directory, you will find five files (``start``, ``end``,
503 show the properties of the region that corresponding DAMON-based operation
557 provides the monitoring results for regions that each DAMON-based Operation
561 :ref:`pattern <damon_design_damos_access_pattern>` based query-like efficient
568 # perf record -e damon:damon_aggregated &
573 …7] 79357.842179: damon:damon_aggregated: target_id=0 nr_regions=11 122509119488-135708762112: 0 864
580 for the target. The eighth field (``X-Y:``) shows the start (``X``) and end
591 …os_before_apply: ctx_idx=0 scheme_idx=0 target_idx=0 nr_regions=11 121932607488-135128711168: 0 136
594 Each line of the output represents each monitoring region that each DAMON-based