From: sashiko-bot@kernel.org
To: "SJ Park" <sj@kernel.org>
Cc: damon@lists.linux.dev
Subject: Re: [PATCH v4 2/3] mm/damon/sysfs: support hugepage_mem_bp quota goal metric
Date: Mon, 31 Aug 2026 18:22:08 +0000 [thread overview]
Message-ID: <20260831182209.6568A1F00A3D@smtp.kernel.org> (raw)
In-Reply-To: <20260831144732.80910-3-sj@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The new `hugepage_mem_bp` metric is missing from the sysfs selftests.
--
commit a2c5ad81dadcc820e74efd9d73c1f576bbe76457
Author: Asier Gutierrez <gutierrez.asier@huawei-partners.com>
mm/damon/sysfs: support hugepage_mem_bp quota goal metric
This commit introduces the new DAMOS_QUOTA_HUGEPAGE_MEM_BP autotune policy
metric. It also exposes this metric to userspace through the sysfs-schemes
interface by adding "hugepage_mem_bp" to the list of recognized metrics.
> diff --git a/mm/damon/sysfs-schemes.c b/mm/damon/sysfs-schemes.c
> index 32f495a96b17a..d9b81d7b5910e 100644
> --- a/mm/damon/sysfs-schemes.c
> +++ b/mm/damon/sysfs-schemes.c
[ ... ]
> @@ -1269,6 +1269,10 @@ struct damos_sysfs_qgoal_metric_name damos_sysfs_qgoal_metric_names[] = {
> .metric = DAMOS_QUOTA_NODE_ELIGIBLE_MEM_BP,
> .name = "node_eligible_mem_bp",
> },
> + {
> + .metric = DAMOS_QUOTA_HUGEPAGE_MEM_BP,
> + .name = "hugepage_mem_bp",
> + },
[Severity: Medium]
Should the new hugepage_mem_bp metric be added to the DAMON sysfs kselftest?
Looking at tools/testing/selftests/damon/sysfs.sh in test_goal(), it explicitly
validates all supported metric strings by writing them to the sysfs node:
ensure_write_succ "$fpath" "node_eligible_mem_bp" "valid input"
ensure_write_fail "$fpath" "foo" "invalid input"
Without adding hugepage_mem_bp to this selftest script, the new sysfs metric
is left without automated test coverage.
> };
>
> static ssize_t target_metric_show(struct kobject *kobj,
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260831144732.80910-1-sj@kernel.org?part=2
next prev parent reply other threads:[~2026-08-31 18:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 14:47 [PATCH v4 0/3] mm/damon: Introduce a huge page collapsing mechanism using auto tuning SJ Park
2026-08-31 14:47 ` [PATCH v4 1/3] mm/damon: Introduce DAMOS_QUOTA_HUGEPAGE " SJ Park
2026-08-31 18:16 ` sashiko-bot
2026-09-01 0:45 ` SJ Park
2026-09-01 6:58 ` Lian Wang
2026-09-01 14:23 ` SJ Park
2026-09-02 1:56 ` Lian Wang
2026-09-02 4:23 ` SJ Park
2026-09-02 15:03 ` Gutierrez Asier
2026-09-02 15:15 ` SJ Park
2026-08-31 14:47 ` [PATCH v4 2/3] mm/damon/sysfs: support hugepage_mem_bp quota goal metric SJ Park
2026-08-31 18:22 ` sashiko-bot [this message]
2026-09-01 0:46 ` SJ Park
2026-08-31 14:47 ` [PATCH v4 3/3] Docs/mm/damon/design: Document hugepage_mem_bp target metric SJ Park
2026-08-31 15:45 ` Randy Dunlap
2026-08-31 20:00 ` Randy Dunlap
2026-09-01 0:47 ` SJ Park
2026-09-01 5:20 ` Gutierrez Asier
2026-09-01 5:31 ` SJ Park
2026-08-31 18:35 ` sashiko-bot
2026-09-01 0:48 ` SJ Park
2026-09-01 0:49 ` [PATCH v4 0/3] mm/damon: Introduce a huge page collapsing mechanism using auto tuning 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=20260831182209.6568A1F00A3D@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=damon@lists.linux.dev \
--cc=sashiko-reviews@lists.linux.dev \
--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