Docs/mm/damon/design: update for address range filters

Update DAMON design document's DAMOS filters section for address range
DAMOS filters.  Because address range filters are handled by the core
layer and it makes difference in schemes tried regions and schemes
statistics, clearly describe it.

Link: https://lkml.kernel.org/r/20230802214312.110532-6-sj@kernel.org
Signed-off-by: SeongJae Park <sj@kernel.org>
Cc: Brendan Higgins <brendanhiggins@google.com>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Shuah Khan <shuah@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
This commit is contained in:
SeongJae Park 2023-08-02 21:43:04 +00:00 committed by Andrew Morton
parent 4c45c20d53
commit 96a7cb2377

View File

@ -380,12 +380,21 @@ number of filters for each scheme. Each filter specifies the type of target
memory, and whether it should exclude the memory of the type (filter-out), or
all except the memory of the type (filter-in).
As of this writing, anonymous page type and memory cgroup type are supported by
the feature. Some filter target types can require additional arguments. For
example, the memory cgroup filter type asks users to specify the file path of
the memory cgroup for the filter. Hence, users can apply specific schemes to
only anonymous pages, non-anonymous pages, pages of specific cgroups, all pages
excluding those of specific cgroups, and any combination of those.
Currently, anonymous page, memory cgroup, and address range type filters are
supported by the feature. Some filter target types can require additional
arguments. For example, the memory cgroup filter type asks users to specify
the file path of the memory cgroup for the filter, while the address range type
asks the start and end addresses of the range. Hence, users can apply specific
schemes to only anonymous pages, non-anonymous pages, pages of specific
cgroups, all pages excluding those of specific cgroups, pages in specific
address range, and any combination of those.
To handle filters efficiently, the address range type filter is handled by the
core layer, while others are handled by operations set. If a memory region is
filtered by the core layer-handled filter, it is not counted as the scheme has
tried to the region. In contrast, if a memory regions is filtered by an
operations set layer-handled filter, it is counted as the scheme has tried.
The difference in accounting leads to changes in the statistics.
Application Programming Interface