tjh.dev / kernel
Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux
1
fork

Configure Feed

Select the types of activity you want to include in your feed.

Docs/mm/damon/design: place execution model and data structures at the beginning

The execution model and data structures section at the end of the design
document is briefly explaining how DAMON works overall. Knowing that
first may help better drawing the overall picture. It may also help
better understanding following detailed sections. Move it to the
beginning of the document.

Link: https://lkml.kernel.org/r/20231213190338.54146-4-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>

authored by

SeongJae Park and committed by
Andrew Morton 1f1d83ca 5e06ad59

+12 -12
+12 -12
Documentation/mm/damon/design.rst
··· 5 5 ====== 6 6 7 7 8 + .. _damon_design_execution_model_and_data_structures: 9 + 10 + Execution Model and Data Structures 11 + =================================== 12 + 13 + The monitoring-related information including the monitoring request 14 + specification and DAMON-based operation schemes are stored in a data structure 15 + called DAMON ``context``. DAMON executes each context with a kernel thread 16 + called ``kdamond``. Multiple kdamonds could run in parallel, for different 17 + types of monitoring. 18 + 19 + 8 20 Overall Architecture 9 21 ==================== 10 22 ··· 502 490 more detail, please read the usage documents for those 503 491 (:doc:`/admin-guide/mm/damon/reclaim` and 504 492 :doc:`/admin-guide/mm/damon/lru_sort`). 505 - 506 - 507 - .. _damon_design_execution_model_and_data_structures: 508 - 509 - Execution Model and Data Structures 510 - =================================== 511 - 512 - The monitoring-related information including the monitoring request 513 - specification and DAMON-based operation schemes are stored in a data structure 514 - called DAMON ``context``. DAMON executes each context with a kernel thread 515 - called ``kdamond``. Multiple kdamonds could run in parallel, for different 516 - types of monitoring.