From: SeongJae Park <sj@kernel.org>
To: sashiko-bot@kernel.org
Cc: SeongJae Park <sj@kernel.org>, damon@lists.linux.dev
Subject: Re: [RFC PATCH v1.1 01/11] Docs/mm/damon/design: update for DAMOS_QUOTA_NODE_ELIGIBLE_MEM_BP
Date: Wed, 24 Jun 2026 22:20:54 -0700 [thread overview]
Message-ID: <20260625052055.92306-1-sj@kernel.org> (raw)
In-Reply-To: <20260625051351.419A51F000E9@smtp.kernel.org>
On Thu, 25 Jun 2026 05:13:50 +0000 sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Low] The patch introduces an internal inconsistency in the design document by documenting the `node_eligible_mem_bp` metric but failing to update the adjacent sentence that lists which metrics require the `nid` parameter.
> --
>
> commit 77a1ee91d398d22fd9a42b16bbf085e55f72a94a
> Author: SeongJae Park <sj@kernel.org>
> Docs/mm/damon/design: update for DAMOS_QUOTA_NODE_ELIGIBLE_MEM_BP
>
> This commit updates the DAMON design document to include the
> node_eligible_mem_bp goal metric that was introduced in an earlier commit.
>
> > diff --git a/Documentation/mm/damon/design.rst b/Documentation/mm/damon/design.rst
> > --- a/Documentation/mm/damon/design.rst
> > +++ b/Documentation/mm/damon/design.rst
> > @@ -686,6 +686,8 @@ mechanism tries to make ``current_value`` of ``target_metric`` be same to
> > (1/10,000).
> > - ``inactive_mem_bp``: Inactive to active + inactive (LRU) memory size ratio in
> > bp (1/10,000).
> > +- ``node_eligible_mem_bp``: Scheme target access pattern-eligible memory ratio
> > + of a node in bp (1/10,000).
> >
> > ``nid`` is optionally required for only ``node_mem_used_bp``,
> > ``node_mem_free_bp``, ``node_memcg_used_bp`` and ``node_memcg_free_bp`` to
>
> [Severity: Low]
> Since node_eligible_mem_bp is a node-specific metric, should it also be
> added to this list of metrics that optionally require nid? As currently
> written, the use of the word "only" implies that node_eligible_mem_bp does
> not use an nid parameter, which could be misleading for users trying to
> configure this metric.
Good catch! I will do so in the next revision.
Thanks,
SJ
[...]
next prev parent reply other threads:[~2026-06-25 5:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-25 5:07 [RFC PATCH v1.1 00/11] mm/damon: update, optimize, and clean up doc, tests, and code SeongJae Park
2026-06-25 5:07 ` [RFC PATCH v1.1 01/11] Docs/mm/damon/design: update for DAMOS_QUOTA_NODE_ELIGIBLE_MEM_BP SeongJae Park
2026-06-25 5:13 ` sashiko-bot
2026-06-25 5:20 ` SeongJae Park [this message]
2026-06-25 5:07 ` [RFC PATCH v1.1 02/11] Docs/ABI/damon: document probe files SeongJae Park
2026-06-25 5:14 ` sashiko-bot
2026-06-25 5:25 ` SeongJae Park
2026-06-25 5:07 ` [RFC PATCH v1.1 03/11] mm/damon/tests/core-kunit: test damon_rand() SeongJae Park
2026-06-25 5:13 ` sashiko-bot
2026-06-25 5:37 ` SeongJae Park
2026-06-25 5:07 ` [RFC PATCH v1.1 04/11] selftests/damon/sysfs.sh: test multiple probe dirs creation SeongJae Park
2026-06-25 5:07 ` [RFC PATCH v1.1 05/11] selftests/damon/sysfs.sh: test {core,ops}_filters/ directories SeongJae Park
2026-06-25 5:07 ` [RFC PATCH v1.1 06/11] selftests/damon/sysfs.sh: test dests dir SeongJae Park
2026-06-25 5:14 ` sashiko-bot
2026-06-25 5:42 ` SeongJae Park
2026-06-25 5:07 ` [RFC PATCH v1.1 07/11] selftests/damon/sysfs.sh: test all files in quota goal dir SeongJae Park
2026-06-25 5:07 ` [RFC PATCH v1.1 08/11] mm/damon/core: reduce range setup in damon_commit_target_regions() SeongJae Park
2026-06-25 5:07 ` [RFC PATCH v1.1 09/11] mm/damon/sysfs: split probe setup function out SeongJae Park
2026-06-25 5:07 ` [RFC PATCH v1.1 10/11] mm/damon/sysfs: split out filters setup function SeongJae Park
2026-06-25 5:07 ` [RFC PATCH v1.1 11/11] mm/damon/sysfs: fix typos in probe_{add,rm}_dirs: s/attr/probe/ 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=20260625052055.92306-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=damon@lists.linux.dev \
--cc=sashiko-bot@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.