From: SJ Park <sj@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Adrian Huang (Lenovo)" <adrianhuang0701@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
Randy Dunlap <rdunlap@infradead.org>, SJ Park <sj@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
damon@lists.linux.dev, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: [PATCH v2 2/3] Docs/admin-guide/mm/damon/lru_sort: fix copy-paste mistakes
Date: Mon, 2 Nov 2026 07:28:46 -0800 [thread overview]
Message-ID: <20261102152849.96057-3-sj@kernel.org> (raw)
In-Reply-To: <20261102152849.96057-1-sj@kernel.org>
From: "Adrian Huang (Lenovo)" <adrianhuang0701@gmail.com>
The DAMON_LRU_SORT documentation mistakenly refers to DAMON_RECLAIM
in a few places.
Fix these copy-paste mistakes to correctly refer to DAMON_LRU_SORT.
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Shuah Khan <skhan@linuxfoundation.org>
Cc: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Adrian Huang (Lenovo) <adrianhuang0701@gmail.com>
Reviewed-by: SJ Park <sj@kernel.org>
Signed-off-by: SJ Park <sj@kernel.org>
---
Documentation/admin-guide/mm/damon/lru_sort.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/admin-guide/mm/damon/lru_sort.rst b/Documentation/admin-guide/mm/damon/lru_sort.rst
index 02ea694426b2c..aa4cc90ca57c6 100644
--- a/Documentation/admin-guide/mm/damon/lru_sort.rst
+++ b/Documentation/admin-guide/mm/damon/lru_sort.rst
@@ -263,7 +263,7 @@ addr_unit
A scale factor for memory addresses and bytes.
This parameter is for setting and getting the :ref:`address unit
-<damon_design_addr_unit>` parameter of the DAMON instance for DAMON_RECLAIM.
+<damon_design_addr_unit>` parameter of the DAMON instance for DAMON_LRU_SORT.
``monitor_region_start`` and ``monitor_region_end`` should be provided in this
unit. For example, let's suppose ``addr_unit``, ``monitor_region_start`` and
@@ -346,7 +346,7 @@ memory regions that not accessed for 120 seconds. The prioritization and
deprioritization is limited to be done using only up to 1% CPU time to avoid
DAMON_LRU_SORT consuming too much CPU time for the (de)prioritization. It also
asks DAMON_LRU_SORT to do nothing if the system's free memory rate is more than
-50%, but start the real works if it becomes lower than 40%. If DAMON_RECLAIM
+50%, but start the real works if it becomes lower than 40%. If DAMON_LRU_SORT
doesn't make progress and therefore the free memory rate becomes lower than
20%, it asks DAMON_LRU_SORT to do nothing again, so that we can fall back to
the LRU-list based page granularity reclamation. ::
--
2.47.3
next prev parent reply other threads:[~2026-11-02 15:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 15:28 [PATCH v2 0/3] Docs/admin-guide/mm/damon: minor fixes SJ Park
2026-11-02 15:28 ` [PATCH v2 1/3] Docs/admin-guide/mm/damon: fix various typos SJ Park
2026-11-02 15:28 ` SJ Park [this message]
2026-11-02 15:28 ` [PATCH v2 3/3] Docs/admin-guide/mm/damon/usage: fix incorrect option syntax in perf example SJ Park
2026-11-02 15:49 ` [PATCH v2 0/3] Docs/admin-guide/mm/damon: minor fixes SJ Park
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261102152849.96057-3-sj@kernel.org \
--to=sj@kernel.org \
--cc=adrianhuang0701@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=damon@lists.linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox