mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2024-09-30 14:19:16 +00:00
c6bb975aa6
Patch series "Docs/mm/damon: Minor fixes and design doc update". Some of the DAMON documents are outdated, or having minor typos or grammar erros. Especially, the design doc has not updated for DAMOS, which is an important part of DAMON. Fix the minor issues and update documents. This patch (of 10): The first two questions of DAMON faqs have raised when DAMON patches were first submitted. More than one year has passed since DAMON patches get merged in the mainline, and that kind of questions are not asked nowadays. Remove the questions. Link: https://lkml.kernel.org/r/20230525214314.5204-1-sj@kernel.org Link: https://lkml.kernel.org/r/20230525214314.5204-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>
27 lines
1.1 KiB
ReStructuredText
27 lines
1.1 KiB
ReStructuredText
.. SPDX-License-Identifier: GPL-2.0
|
|
|
|
==========================
|
|
Frequently Asked Questions
|
|
==========================
|
|
|
|
Does DAMON support virtual memory only?
|
|
=======================================
|
|
|
|
No. The core of the DAMON is address space independent. The address space
|
|
specific monitoring operations including monitoring target regions
|
|
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
|
|
space with any access check technique.
|
|
|
|
Nonetheless, DAMON provides vma/rmap tracking and PTE Accessed bit check based
|
|
implementations of the address space dependent functions for the virtual memory
|
|
and the physical memory by default, for a reference and convenient use.
|
|
|
|
|
|
Can I simply monitor page granularity?
|
|
======================================
|
|
|
|
Yes. You can do so by setting the ``min_nr_regions`` attribute higher than the
|
|
working set size divided by the page size. Because the monitoring target
|
|
regions size is forced to be ``>=page size``, the region split will make no
|
|
effect.
|