All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "SeongJae Park" <sj@kernel.org>
Cc: damon@lists.linux.dev
Subject: Re: [RFC PATCH v2.2 21/28] Docs/admin-guide/mm/damon/usage: document data attributes monitoring
Date: Fri, 15 May 2026 01:06:39 +0000	[thread overview]
Message-ID: <20260515010640.126C6C2BCB3@smtp.kernel.org> (raw)
In-Reply-To: <20260515004433.128933-22-sj@kernel.org>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] The documentation contains a contradiction regarding the sysfs layout for `tried_regions/<N>/`. The sysfs hierarchy tree diagram shows a new `probes` directory containing numbered subdirectories with `hits` files (e.g., `probes/0/hits`), but the text section incorrectly claims a single `probe_hits` file is added directly in the region directory.
- [Low] There are several typographical, grammatical, and formatting errors in the newly added documentation.
--

commit 1f54a921d1c61b444501227d66d664dd4513eef3
Author: SeongJae Park <sj@kernel.org>

Docs/admin-guide/mm/damon/usage: document data attributes monitoring

Update DAMON usage document for the newly added data attributes
monitoring feature.

> diff --git a/Documentation/admin-guide/mm/damon/usage.rst b/Documentation/admin-guide/mm/damon/usage.rst
> index 534e1199cf091..44224da62533e 100644
> --- a/Documentation/admin-guide/mm/damon/usage.rst
> +++ b/Documentation/admin-guide/mm/damon/usage.rst
> @@ -71,6 +71,11 @@ comma (",").
>      │ │ │ │ │ │ intervals/sample_us,aggr_us,update_us
>      │ │ │ │ │ │ │ intervals_goal/access_bp,aggrs,min_sample_us,max_sample_us
>      │ │ │ │ │ │ nr_regions/min,max
> +    │ │ │ │ │ │ :ref:`probes <damon_usage_sysfs_probes>`/nr_probes
> +    │ │ │ │ │ │ │ 0/filters/nr_filters
> +    │ │ │ │ │ │ │ │ │ 0/type,matching,allow

This isn't a bug, but there's a formatting issue here. The indentation skips
from 7 vertical bars on the previous line to 9 vertical bars on this line.

> +    │ │ │ │ │ │ │ │ │ ...
> +    │ │ │ │ │ │ │ │ ...
>      │ │ │ │ │ :ref:`targets <sysfs_targets>`/nr_targets
>      │ │ │ │ │ │ :ref:`0 <sysfs_target>`/pid_target,obsolete_target
>      │ │ │ │ │ │ │ :ref:`regions <sysfs_regions>`/nr_regions

[ ... ]

> @@ -94,7 +99,10 @@ comma (",").
>      │ │ │ │ │ │ │ │ 0/id,weight
>      │ │ │ │ │ │ │ :ref:`stats <sysfs_schemes_stats>`/nr_tried,sz_tried,nr_applied,sz_applied,sz_ops_filter_passed,qt_exceeds,nr_snapshots,max_nr_snapshots
>      │ │ │ │ │ │ │ :ref:`tried_regions <sysfs_schemes_tried_regions>`/total_bytes
> -    │ │ │ │ │ │ │ │ 0/start,end,nr_accesses,age,sz_filter_passed
> +    │ │ │ │ │ │ │ │ 0/start,end,nr_accesses,age,sz_filter_passed,

This isn't a bug, but there is an erroneous trailing comma left at the end of
this line.

> +    │ │ │ │ │ │ │ │ │ probes
> +    │ │ │ │ │ │ │ │ │ │ 0/hits
> +    │ │ │ │ │ │ │ │ │ │ ...
>      │ │ │ │ │ │ │ │ ...
>      │ │ │ │ │ │ ...

[ ... ]

> @@ -221,8 +229,8 @@ contexts/<N>/monitoring_attrs/
>  
>  Files for specifying attributes of the monitoring including required quality
>  and efficiency of the monitoring are in ``monitoring_attrs`` directory.
> -Specifically, two directories, ``intervals`` and ``nr_regions`` exist in this
> -directory.
> +Specifically, two directories, ``intervals``, ``nr_regions`` and ``probes``
> +exist in this directory.

This isn't a bug, but the text now lists three directories ("intervals",
"nr_regions", and "probes") while still stating there are "two directories".

>  Under ``intervals`` directory, three files for DAMON's sampling interval
>  (``sample_us``), aggregation interval (``aggr_us``), and update interval

[ ... ]

> @@ -256,6 +264,27 @@ tuning-applied current values of the two intervals can be read from the
>  ``sample_us`` and ``aggr_us`` files after writing ``update_tuned_intervals`` to
>  the ``state`` file.
>  
> +.. _damon_usage_sysfs_probes:
> +
> +contexts/<N>/monitoring_attrs/probes/
> +-------------------------------------
> +
> +A directory for registering :ref:`data attributes monitoring
> +<damon_design_data_attrs_monitoring>` probes.
> +
> +In the beginning, this directory has only one file, ``nr_probes``.  Writing a
> +number (``N``) to the file creates the number of child directories named ``0``
> +to ``N-1``.  Each directory represents each monitoring probe.
> +
> +In each probe directory, one directory, ``filters`` exist.  The directory

This isn't a bug, but "exist" should probably be "exists" to agree with the
singular subject "one directory".

> +contains files for installingt filters for the probe, that is used to determine

This isn't a bug, but "installingt" appears to be a typo.

> +the data attribute for the probe.
> +
> +In the beginning, ``filters`` directory has only one file, ``nr_filters``.
> +Writing a number (``N``) to the file creates the number of child directories
> +named ``0`` to ``N-1``.  Each directory represents each filter and work in a

This isn't a bug, but "work" should probably be "works" to agree with "Each
directory".

> +way similar to that for :ref:`DAMOS filter <sysfs_filters>`.
> +
>  .. _sysfs_targets:

[ ... ]

> @@ -600,10 +629,13 @@ set the ``access pattern`` as their interested pattern that they want to query.
>  tried_regions/<N>/
>  ------------------
>  
> -In each region directory, you will find five files (``start``, ``end``,
> -``nr_accesses``, ``age``, and ``sz_filter_passed``).  Reading the files will
> -show the properties of the region that corresponding DAMON-based operation
> -scheme ``action`` has tried to be applied.
> +In each region directory, you will find six files (``start``, ``end``,
> +``nr_accesses``, ``age``, ``sz_filter_passed`` and ``probe_hits``).  Reading
> +the files will show the properties of the region that corresponding DAMON-based
> +operation scheme ``action`` has tried to be applied.

Is there a contradiction regarding the sysfs layout for tried_regions/<N>/?

The sysfs hierarchy tree diagram updated earlier in this patch shows a new
"probes" directory containing numbered subdirectories with "hits" files:

    │ │ │ │ │ │ │ │ 0/start,end,nr_accesses,age,sz_filter_passed,
    │ │ │ │ │ │ │ │ │ probes
    │ │ │ │ │ │ │ │ │ │ 0/hits

However, the text here incorrectly claims a single "probe_hits" file is added
directly in the region directory instead of the "probes" subdirectory tree.

> +
> +Reading ``probe_hists`` shows the number of data attributes monitoring
> +probe-hit positive samples of the region.

This isn't a bug, but "probe_hists" is a typo.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260515004433.128933-1-sj@kernel.org?part=21

  reply	other threads:[~2026-05-15  1:06 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-15  0:44 [RFC PATCH v2.2 00/28] mm/damon: introduce data attributes monitoring SeongJae Park
2026-05-15  0:44 ` [RFC PATCH v2.2 01/28] mm/damon/core: introduce struct damon_probe SeongJae Park
2026-05-15  0:44 ` [RFC PATCH v2.2 02/28] mm/damon/core: embed damon_probe objects in damon_ctx SeongJae Park
2026-05-15  1:17   ` sashiko-bot
2026-05-15  0:44 ` [RFC PATCH v2.2 03/28] mm/damon/core: introduce damon_filter SeongJae Park
2026-05-15  1:14   ` sashiko-bot
2026-05-15  0:44 ` [RFC PATCH v2.2 04/28] mm/damon/core: commit probes SeongJae Park
2026-05-15  1:05   ` sashiko-bot
2026-05-15  0:44 ` [RFC PATCH v2.2 05/28] mm/damon/core: introduce damon_region->probe_hits SeongJae Park
2026-05-15  0:54   ` sashiko-bot
2026-05-15  0:44 ` [RFC PATCH v2.2 06/28] mm/damon/core: introduce damon_ops->apply_probes SeongJae Park
2026-05-15  0:53   ` sashiko-bot
2026-05-15  0:44 ` [RFC PATCH v2.2 07/28] mm/damon/core: do data attributes monitoring SeongJae Park
2026-05-15  1:05   ` sashiko-bot
2026-05-15  0:44 ` [RFC PATCH v2.2 08/28] mm/damon/paddr: support " SeongJae Park
2026-05-15  1:29   ` sashiko-bot
2026-05-15  0:44 ` [RFC PATCH v2.2 09/28] mm/damon/sysfs: implement probes dir SeongJae Park
2026-05-15  0:44 ` [RFC PATCH v2.2 10/28] mm/damon/sysfs: implement probe dir SeongJae Park
2026-05-15  1:08   ` sashiko-bot
2026-05-15  0:44 ` [RFC PATCH v2.2 11/28] mm/damon/sysfs: implement filters directory SeongJae Park
2026-05-15  0:44 ` [RFC PATCH v2.2 12/28] mm/damon/sysfs: implement filter dir SeongJae Park
2026-05-15  0:44 ` [RFC PATCH v2.2 13/28] mm/damon/sysfs: implement filter dir files SeongJae Park
2026-05-15  0:44 ` [RFC PATCH v2.2 14/28] mm/damon/sysfs: setup probes on DAMON core API parameters SeongJae Park
2026-05-15  0:44 ` [RFC PATCH v2.2 15/28] mm/damon/sysfs-schemes: implement tried_regions/<r>/probes/ SeongJae Park
2026-05-15  1:27   ` sashiko-bot
2026-05-15  0:44 ` [RFC PATCH v2.2 16/28] mm/damon/sysfs-schemes: implement probe dir SeongJae Park
2026-05-15  0:44 ` [RFC PATCH v2.2 17/28] mm/damon/sysfs-schemes: implement probe/hits file SeongJae Park
2026-05-15  0:44 ` [RFC PATCH v2.2 18/28] mm/damon: trace probe_hits SeongJae Park
2026-05-15  0:44 ` [RFC PATCH v2.2 19/28] selftests/damon/sysfs.sh: test probes dir SeongJae Park
2026-05-15  0:44 ` [RFC PATCH v2.2 20/28] Docs/mm/damon/design: document data attributes monitoring SeongJae Park
2026-05-15  0:44 ` [RFC PATCH v2.2 21/28] Docs/admin-guide/mm/damon/usage: " SeongJae Park
2026-05-15  1:06   ` sashiko-bot [this message]
2026-05-15  0:44 ` [RFC PATCH v2.2 22/28] mm/damon/core: introduce DAMON_FILTER_TYPE_MEMCG SeongJae Park
2026-05-15  1:22   ` sashiko-bot
2026-05-15  0:44 ` [RFC PATCH v2.2 23/28] mm/damon/paddr: support DAMON_FILTER_TYPE_MEMCG SeongJae Park
2026-05-15  0:44 ` [RFC PATCH v2.2 24/28] mm/damon/sysfs: add filters/<F>/path file SeongJae Park
2026-05-15  1:35   ` sashiko-bot
2026-05-15  0:44 ` [RFC PATCH v2.2 25/28] mm/damon/sysfs-schemes: move memcg_path_to_id() to sysfs-common SeongJae Park
2026-05-15  1:24   ` sashiko-bot
2026-05-15  0:44 ` [RFC PATCH v2.2 26/28] mm/damon/sysfs: setup damon_filter->memcg_id from path SeongJae Park
2026-05-15  0:44 ` [RFC PATCH v2.2 27/28] Docs/mm/damon/design: update for memcg damon filter SeongJae Park
2026-05-15  0:44 ` [RFC PATCH v2.2 28/28] Docs/admin-guide/mm/damon/usage: " 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=20260515010640.126C6C2BCB3@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 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.