From: SeongJae Park <sj@kernel.org>
To: SeongJae Park <sj@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
damon@lists.linux.dev, kernel-team@meta.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [RFC PATCH 02/14] mm/damon/core: introduce repeat mode damon_call()
Date: Sun, 6 Jul 2025 14:45:18 -0700 [thread overview]
Message-ID: <20250706214518.56529-1-sj@kernel.org> (raw)
In-Reply-To: <20250706200018.42704-3-sj@kernel.org>
On Sun, 6 Jul 2025 13:00:06 -0700 SeongJae Park <sj@kernel.org> wrote:
> damon_call() can be useful for reading or writing DAMON internal data
> for one time. A common pattern of DAMON core usage from DAMON modules
> is doing such reads and writes repeatedly, for example, to periodically
> update the DAMOS stats. To do that with damon_call(), callers should
> call damon_call() repeatedly, with their own delay loop. Each caller
> doing that is repetitive. Introduce a repeat mode damon_call().
> Callers can use the mode by setting a new field in damon_call_control.
> If the mode is turned on, damon_call() returns success immediately, and
> DAMON repeats invoking the callback function inside the kdamond main
> loop.
>
> Signed-off-by: SeongJae Park <sj@kernel.org>
> ---
[...]
> @@ -2389,6 +2393,7 @@ static void kdamond_usleep(unsigned long usecs)
> static void kdamond_call(struct damon_ctx *ctx, bool cancel)
> {
> struct damon_call_control *control;
> + LIST_HEAD(repeat_controls);
> int ret = 0;
>
> while (true) {
> @@ -2407,8 +2412,18 @@ static void kdamond_call(struct damon_ctx *ctx, bool cancel)
> mutex_lock(&ctx->call_controls_lock);
> list_del(&control->list);
> mutex_unlock(&ctx->call_controls_lock);
> - complete(&control->completion);
> + if (!control->repeat)
> + complete(&control->completion);
> + else
> + list_add(&control->list, &repeat_controls);
> }
> + control = list_first_entry_or_null(&repeat_controls,
> + struct damon_call_control, list);
> + if (!control || cancel)
> + return;
> + mutex_lock(&ctx->call_controls_lock);
> + list_add_tail(&control->list, &ctx->call_controls);
> + mutex_unlock(&ctx->call_controls_lock);
> }
Below fixup should be added on this. Without it, the repeat_controls handling
is never executed, so callback will be invoked only once.
diff --git a/mm/damon/core.c b/mm/damon/core.c
index 7a4dc76dd023..3c0c3cef43e7 100644
--- a/mm/damon/core.c
+++ b/mm/damon/core.c
@@ -2402,7 +2402,7 @@ static void kdamond_call(struct damon_ctx *ctx, bool cancel)
struct damon_call_control, list);
mutex_unlock(&ctx->call_controls_lock);
if (!control)
- return;
+ break;
if (cancel) {
control->canceled = true;
} else {
I'll add this on next version of this series.
Thanks,
SJ
[...]
next prev parent reply other threads:[~2025-07-06 21:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-06 20:00 [RFC PATCH 00/14] mm/damon: remove damon_callback SeongJae Park
2025-07-06 20:00 ` [RFC PATCH 01/14] mm/damon: accept parallel damon_call() requests SeongJae Park
2025-07-06 20:00 ` [RFC PATCH 02/14] mm/damon/core: introduce repeat mode damon_call() SeongJae Park
2025-07-06 21:45 ` SeongJae Park [this message]
2025-07-06 20:00 ` [RFC PATCH 03/14] mm/damon/stat: use damon_call() repeat mode instead of damon_callback SeongJae Park
2025-07-06 20:00 ` [RFC PATCH 04/14] mm/damon/reclaim: " SeongJae Park
2025-07-06 20:00 ` [RFC PATCH 05/14] mm/damon/lru_sort: " SeongJae Park
2025-07-06 20:00 ` [RFC PATCH 06/14] samples/damon/prcl: " SeongJae Park
2025-07-06 20:00 ` [RFC PATCH 07/14] samples/damon/wsse: " SeongJae Park
2025-07-06 20:00 ` [RFC PATCH 08/14] mm/damon/core: do not call ops.cleanup() when destroying targets SeongJae Park
2025-07-06 20:00 ` [RFC PATCH 09/14] mm/damon/core: add cleanup_target() ops callback SeongJae Park
2025-07-06 20:00 ` [RFC PATCH 10/14] mm/damon/vaddr: put pid in cleanup_target() SeongJae Park
2025-07-06 21:48 ` SeongJae Park
2025-07-06 20:00 ` [RFC PATCH 11/14] mm/damon/sysfs: remove damon_sysfs_destroy_targets() SeongJae Park
2025-07-06 20:00 ` [RFC PATCH 12/14] mm/damon/core: destroy targets when kdamond_fn() finish SeongJae Park
2025-07-06 20:00 ` [RFC PATCH 13/14] mm/damon/sysfs: remove damon_sysfs_before_terminate() SeongJae Park
2025-07-06 20:00 ` [RFC PATCH 14/14] mm/damon/core: remove damon_callback 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=20250706214518.56529-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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