From: SJ Park <sj@kernel.org>
Cc: SJ Park <sj@kernel.org>, "Liam R. Howlett" <liam@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Lorenzo Stoakes <ljs@kernel.org>, Michal Hocko <mhocko@suse.com>,
Mike Rapoport <rppt@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Suren Baghdasaryan <surenb@google.com>,
Vlastimil Babka <vbabka@kernel.org>,
damon@lists.linux.dev, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: [RFC PATCH v1.1 5/5] Docs/mm/damon/design: update for pgidle_set probe filter
Date: Wed, 9 Sep 2026 21:09:07 -0700 [thread overview]
Message-ID: <20260910040911.148273-6-sj@kernel.org> (raw)
In-Reply-To: <20260910040911.148273-1-sj@kernel.org>
Update DAMON design document for the newly added pgidle_set probe filter
type.
Signed-off-by: SJ Park <sj@kernel.org>
---
Documentation/mm/damon/design.rst | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/mm/damon/design.rst b/Documentation/mm/damon/design.rst
index 8e980dde362de..cb116a82ff20b 100644
--- a/Documentation/mm/damon/design.rst
+++ b/Documentation/mm/damon/design.rst
@@ -299,6 +299,7 @@ filter types. Currently below filter types are supported.
- ``memcg``: Same to that for DAMOS filters.
- ``pgidle_unset``: Matches if the page for the memory is marked as not
access-idle.
+- ``pgidle_set``: Matches if the page for the memory is marked as access-idle.
If such probes are registered, DAMON executes the probes for each region's
sampling memory when it does the access :ref:`sampling
@@ -314,7 +315,7 @@ actions are registered, DAMON applies the actions to each region's sampling
memory before starting the next sampling interval. Currently only one action,
``set_pgidle`` is supported. The action marks the page for the probing target
memory as access-idle. This can be useful to be used together with
-``pgidle_unset`` probe filter.
+``pgidle_unset`` or ``pgidle_set`` probe filter.
This is a sampling based mechanism. Hence, it is lightweight but the output
may include some measurement errors. The output should be used with good
--
2.47.3
next prev parent reply other threads:[~2026-09-10 4:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 4:09 [RFC PATCH v1.1 0/5] mm/damon: introduce pgidle_set probe filter type SJ Park
2026-09-10 4:09 ` [RFC PATCH v1.1 1/5] mm/damon/api: introduce DAMON_FILTER_TYPE_PGIDLE_SET SJ Park
2026-09-10 4:14 ` sashiko-bot
2026-09-10 4:09 ` [RFC PATCH v1.1 2/5] mm/damon/paddr: support DAMON_FILTER_TYPE_PGIDLE_SET SJ Park
2026-09-10 4:19 ` sashiko-bot
2026-09-10 4:09 ` [RFC PATCH v1.1 3/5] mm/damon/vaddr: " SJ Park
2026-09-10 4:15 ` sashiko-bot
2026-09-10 4:09 ` [RFC PATCH v1.1 4/5] mm/damon/sysfs: " SJ Park
2026-09-10 4:15 ` sashiko-bot
2026-09-10 4:09 ` SJ Park [this message]
2026-09-10 4:10 ` [RFC PATCH v1.1 5/5] Docs/mm/damon/design: update for pgidle_set probe filter sashiko-bot
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=20260910040911.148273-6-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=damon@lists.linux.dev \
--cc=david@kernel.org \
--cc=liam@infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=rdunlap@infradead.org \
--cc=rppt@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=surenb@google.com \
--cc=vbabka@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.