DAMON development mailing list
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: gutierrez.asier@huawei-partners.com
Cc: damon@lists.linux.dev
Subject: Re: [RFC PATCH v3 4/4] Documentation/admin-guide/mm/damon: add DAMON-based Hugepage Management
Date: Thu, 04 Jun 2026 15:48:40 +0000	[thread overview]
Message-ID: <20260604154840.92DB11F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260604150338.501128-5-gutierrez.asier@huawei-partners.com>

Thank you for your contribution! Sashiko AI review found 4 potential issue(s) to consider:
- [Low] The newly added documentation file `hugepage.rst` is orphaned because it is not included in any Sphinx `toctree`.
- [Low] The documentation references an incorrect Kconfig symbol `CONFIG_DAMON_HUGEPAGE` instead of `CONFIG_SAMPLE_DAMON_HUGEPAGE`.
- [Low] Missing newline at the end of the newly added documentation file.
- [Low] Multiple spelling and grammatical errors in the newly added documentation.
--

commit 24c835e6a5624692adf95a519c4c1747fca62d26
Author: Asier Gutierrez <gutierrez.asier@huawei-partners.com>

Documentation/admin-guide/mm/damon: add DAMON-based Hugepage Management

Add documentation for the DAMON-based Hugepage Management
(SAMPLE_DAMON_HUGEPAGE) feature, which automatically manages
huge pages by identifying hot memory regions and collapsing
them back to regular pages.

[Severity: Low]
Is this new documentation file orphaned? It doesn't appear to be added to the
toctree in Documentation/admin-guide/mm/damon/index.rst.

> diff --git a/Documentation/admin-guide/mm/damon/hugepage.rst b/Documentation/admin-guide/mm/damon/hugepage.rst
> new file mode 100644
> index 0000000000000..86104aaa4d1c3
> --- /dev/null
> +++ b/Documentation/admin-guide/mm/damon/hugepage.rst

[ ... ]

> +Interface: Module Parameters
> +============================
> +
> +To use this feature, you should first ensure your system is running on a kernel
> +that is built with ``CONFIG_DAMON_HUGEPAGE=y``.

[Severity: Low]
Does this reference the wrong Kconfig symbol? The module appears to be
SAMPLE_DAMON_HUGEPAGE, so should this be CONFIG_SAMPLE_DAMON_HUGEPAGE=y?

[ ... ]

> +commit_inputs
> +-------------
> +
> +Make SAMPLE_DAMON_HUGEPAGE reads the input parameters again, except ``enabled``.

[Severity: Low]
This isn't a bug, but should "reads" be "read" here?

> +
> +Input parameters that updated while SAMPLE_DAMON_HUGEPAGE is running are

[Severity: Low]
This isn't a bug, but should this be "parameters that are updated"?

[ ... ]

> +quota_reset_interval_ms
> +-----------------------
> +
> +The time/size quota charge reset interval in milliseconds.
> +
> +The charget reset interval for the quota of time (quota_ms) and size

[Severity: Low]
This isn't a bug, but there is a typo here ("charget" -> "charge").

[ ... ]

> +quota_autotune_feedback
> +-----------------------
> +
> +User-specifiable feedback for auto-tuning of the effective quota.
> +
> +While keeping the caps that set by other quotas, SAMPLE_DAMON_HUGEPAGE
> +automatically increases and decreases the effective level of the quota
> +aiming receiving this feedback of value ``10,000`` from the user.

[Severity: Low]
This isn't a bug, but should this be "aiming to receive"?

[ ... ]

> +Example
> +=======
> +
> +Below runtime example commands make SAMPLE_DAMON_HUGEPAGE to find memory
> +regions of  the task with PID 1234 that have been accessed in the last 100
> +milliseconds or more and collpases those pages into huge pages. The page

[Severity: Low]
This isn't a bug, but there is a typo here ("collpases" -> "collapses").

[ ... ]

> +Note that this module (SAMPLE_DAMON_HUGEPAGE) cannot run simultaneously
> +with other DAMON-based special-purpose modules.  Refer to
> + :ref:`DAMON design special purpose modules exclusivity
> + <damon_design_special_purpose_modules_exclusivity>` for more details.
> \ No newline at end of file

[Severity: Low]
This isn't a bug, but could we add a newline at the end of the file?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260604150338.501128-1-gutierrez.asier@huawei-partners.com?part=4

  reply	other threads:[~2026-06-04 15:48 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-04 15:03 [RFC PATCH v3 0/4] mm/damon: Introduce a huge page collapsing mechanism using auto tuning gutierrez.asier
2026-06-04 15:03 ` [RFC PATCH v3 1/4] mm/damon: Introduce DAMOS_QUOTA_HUGEPAGE " gutierrez.asier
2026-06-04 15:19   ` sashiko-bot
2026-06-05 10:57     ` Gutierrez Asier
2026-06-06  0:12       ` SeongJae Park
2026-06-09 11:01         ` Gutierrez Asier
2026-06-09 14:52           ` SeongJae Park
2026-06-05  0:44   ` SeongJae Park
2026-06-05 11:00     ` Gutierrez Asier
2026-06-06  0:14       ` SeongJae Park
2026-06-04 15:03 ` [RFC PATCH v3 2/4] mm/damon: Generalize ctx_target creation for damon_ops_id and add vaddr support gutierrez.asier
2026-06-05  0:50   ` SeongJae Park
2026-06-05 11:13     ` Gutierrez Asier
2026-06-06  0:15       ` SeongJae Park
2026-06-04 15:03 ` [RFC PATCH v3 3/4] mm/damon: introduce DAMON_HUGEPAGE for hot region hugepage collapsing gutierrez.asier
2026-06-04 15:41   ` sashiko-bot
2026-06-05 14:16     ` Gutierrez Asier
2026-06-05  1:06   ` SeongJae Park
2026-06-05 13:47     ` Gutierrez Asier
2026-06-04 15:03 ` [RFC PATCH v3 4/4] Documentation/admin-guide/mm/damon: add DAMON-based Hugepage Management gutierrez.asier
2026-06-04 15:48   ` sashiko-bot [this message]
2026-06-05  1:09   ` SeongJae Park
2026-06-05 10:28     ` Gutierrez Asier
2026-06-05  1:34 ` [RFC PATCH v3 0/4] mm/damon: Introduce a huge page collapsing mechanism using auto tuning SeongJae Park
2026-06-05 10:25   ` Gutierrez Asier
2026-06-06  0:24     ` SeongJae 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=20260604154840.92DB11F00893@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=damon@lists.linux.dev \
    --cc=gutierrez.asier@huawei-partners.com \
    --cc=sashiko-reviews@lists.linux.dev \
    /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