[PATCH 01/10] Docs/mm/damon/faq: remove old questions

From: SeongJae Park
Date: Thu May 25 2023 - 17:43:29 EST

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.

Signed-off-by: SeongJae Park <sj@xxxxxxxxxx>
Documentation/mm/damon/faq.rst | 23 -----------------------
1 file changed, 23 deletions(-)

diff --git a/Documentation/mm/damon/faq.rst b/Documentation/mm/damon/faq.rst
index dde7e2414ee6..3279dc7a8211 100644
--- a/Documentation/mm/damon/faq.rst
+++ b/Documentation/mm/damon/faq.rst
@@ -4,29 +4,6 @@
Frequently Asked Questions

-Why a new subsystem, instead of extending perf or other user space tools?
-First, because it needs to be lightweight as much as possible so that it can be
-used online, any unnecessary overhead such as kernel - user space context
-switching cost should be avoided. Second, DAMON aims to be used by other
-programs including the kernel. Therefore, having a dependency on specific
-tools like perf is not desirable. These are the two biggest reasons why DAMON
-is implemented in the kernel space.
-Can 'idle pages tracking' or 'perf mem' substitute DAMON?
-Idle page tracking is a low level primitive for access check of the physical
-address space. 'perf mem' is similar, though it can use sampling to minimize
-the overhead. On the other hand, DAMON is a higher-level framework for the
-monitoring of various address spaces. It is focused on memory management
-optimization and provides sophisticated accuracy/overhead handling mechanisms.
-Therefore, 'idle pages tracking' and 'perf mem' could provide a subset of
-DAMON's output, but cannot substitute DAMON.
Does DAMON support virtual memory only?