Lines Matching +full:monitor +full:- +full:interval +full:- +full:ms
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.*
40 For a short example, users can monitor the virtual address space of a given
51 ---------------
54 figure, parents-children relations are represented with indentations, each
58 .. parsed-literal::
80 │ │ │ │ │ │ │ :ref:`quotas <sysfs_quotas>`/ms,bytes,reset_interval_ms,effective_bytes
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 -------------
196 ------------------------------
203 Under ``intervals`` directory, three files for DAMON's sampling interval
204 (``sample_us``), aggregation interval (``aggr_us``), and update 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 ---------------------
223 to ``N-1``. Each directory represents each monitoring target.
228 ------------
240 -------------------
253 to ``N-1``. Each directory represents each initial monitoring target region.
258 ------------
270 ---------------------
272 The directory for DAMON-based Operation Schemes (:ref:`DAMOS
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.
314 and the ``max`` form a closed interval.
319 -------------------
322 DAMON-based operation scheme.
324 Under ``quotas`` directory, four files (``ms``, ``bytes``,
329 ``reset interval`` in milliseconds by writing the values to the three files,
333 ``reset_interval_ms``. Setting both ``ms`` and ``bytes`` zero disables 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
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.
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
391 - none: Ignore the watermarks
392 - free_mem_rate: System's free memory rate (per thousand)
394 The ``interval`` should written in microseconds unit.
399 --------------------
402 DAMON-based operation scheme.
406 to ``N-1``. Each directory represents each filter. The filters are evaluated
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 ------------------
469 --------------------------
479 this directory, during next :ref:`apply interval <damon_design_damos>` of the
492 and query-like efficient data access monitoring results retrievals. For the
499 ------------------
503 show the properties of the region that corresponding DAMON-based operation
510 8KiB] is showing accesses per aggregate interval in [0, 5] for aggregate
511 interval in [10, 20], page out the region. For the paging out, use only up to
512 10ms per second, and also don't page out more than 1GiB per second. Under the
532 # echo 10 > quotas/ms
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