leandrof/linux
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Docs/vm/damon: call low level monitoring primitives the operations

Browse Source 
Patch series "Docs/damon: Update documents for better consistency".

Some of DAMON document are not properly updated for latest version.  This
patchset updates such parts.

This patch (of 3):

DAMON code calls the low level monitoring primitives implementations the
monitoring operations.  The documentation would have no problem at still
calling those primitives implementation because there is no real
difference in the concepts, but making it more consistent with the code
would make it better.  This commit therefore convert sentences in the doc
specifically pointing the implementations of the primitives to call it
monitoring operations.

Link: https://lkml.kernel.org/r/20220222170100.17068-1-sj@kernel.org
Link: https://lkml.kernel.org/r/20220222170100.17068-2-sj@kernel.org
Signed-off-by: SeongJae Park <sj@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
SeongJae Park 2022-03-22 14:49:12 -07:00 committed by Linus Torvalds
parent 3213a3c10f
commit 561f4fc497
2 changed files with 13 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
Documentation/vm/damon/design.rst
View File

@ -13,12 +13,13 @@ primitives that dependent on and optimized for the target address space. On
the other hand, the accuracy and overhead tradeoff mechanism, which is the core the other hand, the accuracy and overhead tradeoff mechanism, which is the core
of DAMON, is in the pure logic space. DAMON separates the two parts in of DAMON, is in the pure logic space. DAMON separates the two parts in
different layers and defines its interface to allow various low level different layers and defines its interface to allow various low level
primitives implementations configurable with the core logic. primitives implementations configurable with the core logic. We call the low
level primitives implementations monitoring operations.
Due to this separated design and the configurable interface, users can extend Due to this separated design and the configurable interface, users can extend
DAMON for any address space by configuring the core logics with appropriate low DAMON for any address space by configuring the core logics with appropriate
level primitive implementations. If appropriate one is not provided, users can monitoring operations. If appropriate one is not provided, users can implement
implement the primitives on their own. the operations on their own.
For example, physical memory, virtual memory, swap space, those for specific For example, physical memory, virtual memory, swap space, those for specific
processes, NUMA nodes, files, and backing memory devices would be supportable. processes, NUMA nodes, files, and backing memory devices would be supportable.
@ -26,25 +27,24 @@ Also, if some architectures or devices support special optimized access check
primitives, those will be easily configurable. primitives, those will be easily configurable.
Reference Implementations of Address Space Specific Primitives Reference Implementations of Address Space Specific Monitoring Operations
============================================================== =========================================================================
The low level primitives for the fundamental access monitoring are defined in The monitoring operations are defined in two parts:
two parts:
1. Identification of the monitoring target address range for the address space. 1. Identification of the monitoring target address range for the address space.
2. Access check of specific address range in the target space. 2. Access check of specific address range in the target space.
DAMON currently provides the implementations of the primitives for the physical DAMON currently provides the implementations of the operations for the physical
and virtual address spaces. Below two subsections describe how those work. and virtual address spaces. Below two subsections describe how those work.
VMA-based Target Address Range Construction VMA-based Target Address Range Construction
------------------------------------------- -------------------------------------------
This is only for the virtual address space primitives implementation. That for This is only for the virtual address space monitoring operations
the physical address space simply asks users to manually set the monitoring implementation. That for the physical address space simply asks users to
target address ranges. manually set the monitoring target address ranges.
Only small parts in the super-huge virtual address space of the processes are Only small parts in the super-huge virtual address space of the processes are
mapped to the physical memory and accessed. Thus, tracking the unmapped mapped to the physical memory and accessed. Thus, tracking the unmapped

2
Documentation/vm/damon/faq.rst
View File

@ -31,7 +31,7 @@ Does DAMON support virtual memory only?
======================================= =======================================
No. The core of the DAMON is address space independent. The address space No. The core of the DAMON is address space independent. The address space
specific low level primitive parts including monitoring target regions specific monitoring operations including monitoring target regions
constructions and actual access checks can be implemented and configured on the constructions and actual access checks can be implemented and configured on the
DAMON core by the users. In this way, DAMON users can monitor any address DAMON core by the users. In this way, DAMON users can monitor any address
space with any access check technique. space with any access check technique.