@@ -16,16 +16,16 @@ monitoring :ref:`mechanisms <damon_design_monitoring>` of DAMON make it
16
16
of the size of target workloads).
17
17
18
18
Using this framework, therefore, the kernel can operate system in an
19
- access-aware fashion. Because the features are also exposed to the user space,
20
- users who have special information about their workloads can write personalized
21
- applications for better understanding and optimizations of their workloads and
22
- systems.
19
+ access-aware fashion. Because the features are also exposed to the :doc: ` user
20
+ space </admin-guide/mm/damon/index>`, users who have special information about
21
+ their workloads can write personalized applications for better understanding
22
+ and optimizations of their workloads and systems.
23
23
24
24
For easier development of such systems, DAMON provides a feature called
25
25
:ref: `DAMOS <damon_design_damos >` (DAMon-based Operation Schemes) in addition
26
- to the monitoring. Using the feature, DAMON users in both kernel and user
27
- spaces can do access-aware system operations with no code but simple
28
- configurations.
26
+ to the monitoring. Using the feature, DAMON users in both kernel and :doc: ` user
27
+ spaces </admin-guide/mm/damon/index>` can do access-aware system operations
28
+ with no code but simple configurations.
29
29
30
30
.. toctree ::
31
31
:maxdepth: 2
@@ -34,3 +34,6 @@ configurations.
34
34
design
35
35
api
36
36
maintainer-profile
37
+
38
+ To utilize and control DAMON from the user-space, please refer to the
39
+ administration :doc: `guide </admin-guide/mm/damon/index >`.
0 commit comments