Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Manuel Ebner" <manuelebnerli@mailbox.org>,
	"SJ Park" <sj@kernel.org>, "Jonathan Corbet" <corbet@lwn.net>,
	"Shuah Khan" <skhan@linuxfoundation.org>,
	"Randy Dunlap" <rdunlap@infradead.org>
Cc: "Aveline Noir" <jm5905938@gmail.com>,
	damon@lists.linux.dev, linux-mm@kvack.org
Subject: Re: [PATCH v3] Docs/admin-guide/mm/damon/reclaim: improve language
Date: Tue, 03 Nov 2026 12:04:04 +0000	[thread overview]
Message-ID: <sashiko-outbox-195212@kernel.org> (raw)
In-Reply-To: <20261103120043.100887-2-manuelebnerli@mailbox.org>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Docs/mm/damon: typo 'aimes' introduced in reclaim.rst
--

commit 553db5dbc4617619eacc8a4470aca6b0504960ff
Author: Manuel Ebner <manuelebnerli@mailbox.org>

Docs/admin-guide/mm/damon/reclaim: improve language

This commit improves the grammar, tense consistency, and phrasing in the
DAMON_RECLAIM administration guide documentation.

> diff --git a/Documentation/admin-guide/mm/damon/reclaim.rst b/Documentation/admin-guide/mm/damon/reclaim.rst
> index 028947f5da8ec..aeb2770f1d03e 100644
> --- a/Documentation/admin-guide/mm/damon/reclaim.rst
> +++ b/Documentation/admin-guide/mm/damon/reclaim.rst
> @@ -4,7 +4,7 @@
>  DAMON-based Reclamation
>  =======================
>  
> -DAMON-based Reclamation (DAMON_RECLAIM) is a static kernel module that aimed to
> +DAMON-based reclamation (DAMON_RECLAIM) is a static kernel module that aimes to
>  be used for proactive and lightweight reclamation under light memory pressure.
>  It doesn't aim to replace the LRU-list based page_granularity reclamation, but
>  to be selectively used for different level of memory pressure and requirements.

[Severity: Low]
In the DAMON-based Reclamation introduction in
Documentation/admin-guide/mm/damon/reclaim.rst, "aimes" is a typo. Should
this be "aims" instead?

[ ... ]

> @@ -88,7 +89,7 @@ identifies the region as cold, and reclaims it.
>  autotune_monitoring_intervals
>  -----------------------------
>  
> -If this parameter is set as ``Y``, DAMON_RECLAIM automatically tunes DAMON's
> +If this parameter is set to ``Y``, DAMON_RECLAIM automatically tunes DAMON's
>  sampling and aggregation intervals.  The auto-tuning aims to capture meaningful
>  amount of access events in each DAMON-snapshot, while keeping the sampling
>  interval 5 milliseconds in minimum, and 10 seconds in maximum.  Setting this as
> @@ -113,10 +114,10 @@ quota_sz

[ ... ]

> @@ -137,7 +138,7 @@ quota_mem_pressure_us
>  
>  Desired level of memory pressure-stall time in microseconds.
>  
> -While keeping the caps that set by other quotas, DAMON_RECLAIM automatically
> +While keeping the caps that are set by other quotas, DAMON_RECLAIM automatically
>  increases and decreases the effective level of the quota aiming this level of
>  memory pressure is incurred.  System-wide ``some`` memory PSI in microseconds
>  per quota reset interval (``quota_reset_interval_ms``) is collected and

Also, this isn't a bug, but in the autotune_monitoring_intervals section just
above:

  Setting this as ``N`` disables the auto-tuning.

and in the quota_autotune_feedback section just below quota_mem_pressure_us:

  While keeping the caps that set by other quotas, DAMON_RECLAIM automatically

should those also be updated to "Setting this to" and "that are set by" to
match the changes in this patch?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261103120043.100887-2-manuelebnerli@mailbox.org?part=1


  reply	other threads:[~2026-11-03 12:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03 12:00 [PATCH v3] Docs/admin-guide/mm/damon/reclaim: improve language Manuel Ebner
2026-11-03 12:04 ` sashiko-bot [this message]
2026-11-03 15:05 ` 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=sashiko-outbox-195212@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=corbet@lwn.net \
    --cc=damon@lists.linux.dev \
    --cc=jm5905938@gmail.com \
    --cc=linux-mm@kvack.org \
    --cc=manuelebnerli@mailbox.org \
    --cc=rdunlap@infradead.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=sj@kernel.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