Lines Matching +full:allow +full:- +full:set +full:- +full:time
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.*
51 ---------------
54 figure, parents-children relations are represented with indentations, each
58 .. parsed-literal::
86 │ │ │ │ │ │ │ │ 0/type,matching,allow,memcg_path,addr_start,addr_end,target_idx
98 ----
108 ---------
115 child directories named ``0`` to ``N-1``. Each directory represents each
121 -------------
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
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
162 ----------------------
166 ``0`` to ``N-1``. Each directory represents each monitoring context (refer to
174 -------------
183 monitoring operations set on the currently running kernel by reading
189 You can set and get what type of monitoring operations DAMON will use for the
196 ------------------------------
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
210 controls the monitoring overhead, exist. You can set and get the values by
219 ---------------------
223 to ``N-1``. Each directory represents each monitoring target.
228 ------------
240 -------------------
243 required to set the monitoring target address ranges. In case of ``vaddr``
244 operations set, it is not mandatory, but users can optionally set the initial
248 For such cases, users can explicitly set the initial monitoring target regions
253 to ``N-1``. Each directory represents each initial monitoring target region.
258 ------------
261 can set and get the start and end addresses of the initial monitoring target
270 ---------------------
272 The directory for DAMON-based Operation Schemes (:ref:`DAMOS
273 <damon_design_damos>`). Users can get and set the schemes by reading from and
278 to ``N-1``. Each directory represents each DAMON-based operation scheme.
283 ------------
304 ---------------------------
307 <damon_design_damos_access_pattern>` of the given DAMON-based operation scheme.
311 exist. You can set and get the access pattern for the given scheme by writing
319 -------------------
322 DAMON-based operation scheme.
328 You can set the ``time quota`` in milliseconds, ``size quota`` in bytes, and
330 respectively. Then, DAMON tries to use only up to ``time quota`` milliseconds
335 set.
337 The time quota is internally transformed to a size quota. Between the
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
341 the current effective size quota. The file is not updated in real time, so
348 You can set the :ref:`prioritization weights
350 in per-thousand unit by writing the values to the three files under the
356 -------------------------
359 <damon_design_damos_quotas_auto_tuning>` of the given DAMON-based operation
364 to ``N-1``. Each directory represents each goal and current achievement.
368 ``target_value`` and ``current_value``. Users can set and get the three
369 parameters for the quota auto-tuning goals that specified on the :ref:`design
378 -----------------------
381 given DAMON-based operation scheme.
384 ``high``, ``mid``, and ``low``) for setting the metric, the time interval
385 between check of the metric, and the three watermarks exist. You can set and
391 - none: Ignore the watermarks
392 - free_mem_rate: System's free memory rate (per thousand)
399 --------------------
402 DAMON-based operation scheme.
406 to ``N-1``. Each directory represents each filter. The filters are evaluated
410 ``allow``, ``memcg_path``, ``addr_start``, ``addr_end``, and ``target_idx``.
413 pages, ``addr`` for specific address range (an open-ended interval), or
428 ``allow`` file to specify if applying the action to the memory that satisfies
431 For example, below restricts a DAMOS action to be applied to only non-anonymous
438 echo N > 0/allow
443 echo N > 1/allow
447 of different ``allow`` works, when each of the filters are supported, and
453 ------------------
462 updated in real time, so you should ask DAMON sysfs interface to update the
469 --------------------------
492 and query-like efficient data access monitoring results retrievals. For the
493 latter use case, in particular, users can set the ``action`` as ``stat`` and
494 set the ``access pattern`` as their interested pattern that they want to query.
499 ------------------
503 show the properties of the region that corresponding DAMON-based operation
523 # # set the basic access pattern and the action
531 # # set quotas
535 # # set watermark
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
595 Operation Scheme was about to be applied at the traced time. The first five