public inbox for linux-mm@kvack.org
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: SeongJae Park <sj@kernel.org>
Cc: "Liam R. Howlett" <Liam.Howlett@oracle.com>,
	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>,
	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: Re: [RFC PATCH v2 03/10] Docs/mm/damon/design: update for context pause/resume feature
Date: Fri, 20 Mar 2026 08:17:28 -0700	[thread overview]
Message-ID: <20260320151729.99156-1-sj@kernel.org> (raw)
In-Reply-To: <20260319052157.99433-4-sj@kernel.org>

On Wed, 18 Mar 2026 22:21:46 -0700 SeongJae Park <sj@kernel.org> wrote:

> Update DAMON design document for the context execution pause/resume
> feature.
> 
> Signed-off-by: SeongJae Park <sj@kernel.org>
> ---
>  Documentation/mm/damon/design.rst | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/Documentation/mm/damon/design.rst b/Documentation/mm/damon/design.rst
> index 838b14d225193..e2e4fe3fb3986 100644
> --- a/Documentation/mm/damon/design.rst
> +++ b/Documentation/mm/damon/design.rst
> @@ -19,6 +19,13 @@ types of monitoring.
>  To know how user-space can do the configurations and start/stop DAMON, refer to
>  :ref:`DAMON sysfs interface <sysfs_interface>` documentation.
>  
> +Users can also request each context execution to be paused and resumed.  When
> +it is paused, the kdamond does nothing but only online parameters updates
> +including resume request handling.

Sashiko comment
(https://sashiko.dev/#/patchset/20260319052157.99433-4-sj@kernel.org) below.

: This isn't a bug, but the phrasing "does nothing but only online parameters
: updates" is a bit awkward. Could this be reworded for clarity, perhaps to
: something like "does nothing other than apply online parameter updates"?

I pretty sure Sashiko is more English fluent than I.  But, shouldn't
's/apply/applying/' ?  I will update the sentence to "When it is paused, the
kdamond does nothing other than applying online parameter update" in the next
revision.


Thanks,
SJ

[...]


  reply	other threads:[~2026-03-20 15:17 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
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 [this message]
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=20260320151729.99156-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=damon@lists.linux.dev \
    --cc=david@kernel.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox