From: SeongJae Park <sj@kernel.org>
To: SeongJae Park <sj@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
damon@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [RFC PATCH v2 01/10] mm/damon/core: introduce damon_ctx->paused
Date: Wed, 18 Mar 2026 23:29:10 -0700 [thread overview]
Message-ID: <20260319062911.77252-1-sj@kernel.org> (raw)
In-Reply-To: <20260319052157.99433-2-sj@kernel.org>
On Wed, 18 Mar 2026 22:21:44 -0700 SeongJae Park <sj@kernel.org> wrote:
> DAMON supports only start and stop of the execution. When it is
> stopped, its internal data that it self-trained goes away. It will be
> useful if the execution can be paused and resumed with the previous
> self-trained data.
>
> Introduce per-context API parameter, 'paused', for the purpose. The
> parameter can be set and unset while DAMON is running and paused, using
> the online parameters commit helper functions (damon_commit_ctx() and
> damon_call()). Once 'paused' is set, the kdamond_fn() main loop does
> only limited works with sampling interval sleep during the works. The
> limited works include the handling of the online parameters update, so
> that users can unset the 'pause' and resume the execution when they
> want. It also keep checking DAMON stop conditions and handling of it,
> so that DAMON can be stopped while paused if needed.
>
> Signed-off-by: SeongJae Park <sj@kernel.org>
> ---
> include/linux/damon.h | 2 ++
> mm/damon/core.c | 9 +++++++++
> 2 files changed, 11 insertions(+)
>
> diff --git a/include/linux/damon.h b/include/linux/damon.h
> index 3a441fbca170d..421e51eff3bd2 100644
> --- a/include/linux/damon.h
> +++ b/include/linux/damon.h
> @@ -811,6 +811,8 @@ struct damon_ctx {
> * intervals tuning
> */
> unsigned long next_intervals_tune_sis;
> + /* pause kdamond main loop */
> + bool pause;
This field will be directly set by an API caller. But this diff is defining
this field in the private fields section. I will change this to be defined in
the public fields section, and add the kernel-doc comment, in the next version.
Thanks,
SJ
[...]
next prev parent reply other threads:[~2026-03-19 6:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 5:21 [RFC PATCH v2 00/10] mm/damon: let DAMON be paused and resumed SeongJae Park
2026-03-19 5:21 ` [RFC PATCH v2 01/10] mm/damon/core: introduce damon_ctx->paused SeongJae Park
2026-03-19 6:29 ` SeongJae Park [this message]
2026-03-20 15:11 ` SeongJae Park
2026-03-19 5:21 ` [RFC PATCH v2 02/10] mm/damon/sysfs: add pause file under context dir SeongJae Park
2026-03-19 5:21 ` [RFC PATCH v2 03/10] Docs/mm/damon/design: update for context pause/resume feature SeongJae Park
2026-03-20 15:17 ` SeongJae Park
2026-03-19 5:21 ` [RFC PATCH v2 04/10] Docs/admin-guide/mm/damon/usage: update for pause file SeongJae Park
2026-03-19 5:21 ` [RFC PATCH v2 05/10] Docs/ABI/damon: update for pause sysfs file SeongJae Park
2026-03-19 5:21 ` [RFC PATCH v2 06/10] mm/damon/tests/core-kunit: test pause commitment SeongJae Park
2026-03-19 5:21 ` [RFC PATCH v2 07/10] selftests/damon/_damon_sysfs: support pause file staging SeongJae Park
2026-03-20 15:22 ` SeongJae Park
2026-03-19 5:21 ` [RFC PATCH v2 08/10] selftests/damon/drgn_dump_damon_status: dump pause SeongJae Park
2026-03-19 5:21 ` [RFC PATCH v2 09/10] selftests/damon/sysfs.py: check pause on assert_ctx_committed() SeongJae Park
2026-03-19 5:21 ` [RFC PATCH v2 10/10] selftets/damon/sysfs.py: pause DAMON before dumping status SeongJae Park
2026-03-20 15:29 ` SeongJae Park
2026-03-20 15:41 ` SeongJae Park
2026-03-21 1:02 ` 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=20260319062911.77252-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--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