From: Liew Rui Yan <aethernet65535@gmail.com>
To: SJ Park <sj@kernel.org>
Cc: damon@lists.linux.dev, linux-mm@kvack.org,
Liew Rui Yan <aethernet65535@gmail.com>
Subject: [PATCH 3/3] docs/mm/damon/design: fix typo of max_nr_snapshots
Date: Tue, 11 Aug 2026 18:18:41 +0800 [thread overview]
Message-ID: <20260811101841.804596-4-aethernet65535@gmail.com> (raw)
In-Reply-To: <20260811101841.804596-1-aethernet65535@gmail.com>
Fixes a typo (nr_snapshots -> max_nr_snapshots) and corrects a grammar
error.
Signed-off-by: Liew Rui Yan <aethernet65535@gmail.com>
---
Documentation/mm/damon/design.rst | 4 ++--
include/linux/damon.h | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/mm/damon/design.rst b/Documentation/mm/damon/design.rst
index 1fcf0b8c044b..62ba6cc2e999 100644
--- a/Documentation/mm/damon/design.rst
+++ b/Documentation/mm/damon/design.rst
@@ -871,8 +871,8 @@ action is ``pageout`` while all pages of the region are unreclaimable, applying
the action to the region will fail.
Unlike normal stats, ``max_nr_snapshots`` is set by users. If it is set as
-non-zero and ``nr_snapshots`` be same to or greater than ``nr_snapshots``, the
-scheme is deactivated. Note that, unlike watermarks, even if a scheme's
+non-zero and ``nr_snapshots`` equals or is greater than ``max_nr_snapshots``,
+the scheme is deactivated. Note that, unlike watermarks, even if a scheme's
``nr_snapshots`` reaches ``max_nr_snapshots``, monitoring will not stop.
To know how user-space can read the stats via :ref:`DAMON sysfs interface
diff --git a/include/linux/damon.h b/include/linux/damon.h
index d642ce4fc83c..75ece3d03be2 100644
--- a/include/linux/damon.h
+++ b/include/linux/damon.h
@@ -549,7 +549,7 @@ struct damos_migrate_dests {
*
* After applying the &action to each region, &stat is updated.
*
- * If &max_nr_snapshots is set as non-zero and &stat.nr_snapshots be same to or
+ * If &max_nr_snapshots is set as non-zero and &stat.nr_snapshots equals or is
* greater than it, the scheme is deactivated.
*/
struct damos {
--
2.55.0
next prev parent reply other threads:[~2026-08-11 10:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 10:18 [PATCH 0/3] docs/mm/damon/design: add explanation of nr_snapshots Liew Rui Yan
2026-08-11 10:18 ` [PATCH 1/3] docs/mm/damon/design: accurate semantics " Liew Rui Yan
2026-08-11 13:46 ` SJ Park
2026-08-11 17:01 ` Liew Rui Yan
2026-08-11 10:18 ` [PATCH 2/3] docs/mm/damon/design: difference between watermarks and nr_snapshots Liew Rui Yan
2026-08-11 13:48 ` SJ Park
2026-08-11 10:18 ` Liew Rui Yan [this message]
2026-08-11 13:52 ` [PATCH 3/3] docs/mm/damon/design: fix typo of max_nr_snapshots SJ Park
2026-08-11 13:56 ` [PATCH 0/3] docs/mm/damon/design: add explanation of nr_snapshots SJ Park
2026-08-11 17:02 ` Liew Rui Yan
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=20260811101841.804596-4-aethernet65535@gmail.com \
--to=aethernet65535@gmail.com \
--cc=damon@lists.linux.dev \
--cc=linux-mm@kvack.org \
--cc=sj@kernel.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