From: SeongJae Park <sj@kernel.org>
To: Sang-Heon Jeon <ekffu200098@gmail.com>
Cc: SeongJae Park <sj@kernel.org>,
honggyu.kim@sk.com, damon@lists.linux.dev, linux-mm@kvack.org
Subject: Re: [PATCH] mm/damon: update expired description of damos_action
Date: Thu, 31 Jul 2025 10:58:27 -0700 [thread overview]
Message-ID: <20250731175827.16060-1-sj@kernel.org> (raw)
In-Reply-To: <20250731132230.80046-1-ekffu200098@gmail.com>
Hello Sang-Heon,
On Thu, 31 Jul 2025 22:22:30 +0900 Sang-Heon Jeon <ekffu200098@gmail.com> wrote:
> Nowadays, damos operation actions support more various operation set.
> But comments(also, generated documentation) doesn't updated.
> So, fix the comments with current support status.
Thank you for catching this and fixing!
>
> Signed-off-by: Sang-Heon Jeon <ekffu200098@gmail.com>
> ---
> I also found below patch(https://lore.kernel.org/damon/20250730200239.60984-1-sj@kernel.org/T/#t)
> So, Is it means that DAMOS_STAT is only supported by paddr now?
No. 'vaddr' supports DAMOS_STAT. The patch is not adding DAMOS_STAT support
on vaddr, but extending the support for DAMOS filters.
Thank you for checking the thread and asking this question, though. I see this
as an important signal of another rooms to improve on the documentation.
> If my understanding is correct, then we need to fix Design documentation
> and comments both.
>
> However, since it will be fixed soon. Keeping current status is also
> affordable. So could you check this point as well?
>
> ---
>
> include/linux/damon.h | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/include/linux/damon.h b/include/linux/damon.h
> index cddf82eaac4e..0870e9f48b0f 100644
> --- a/include/linux/damon.h
> +++ b/include/linux/damon.h
> @@ -128,7 +128,7 @@ struct damon_access_report {
Seems you are using damon/next as your baseline. If there is no real
dependencies to damon/next, please use mm-new as your baseline. For more
contexts about that, please refer to the DAMON maintainer-profile[1].
> *
> * @DAMOS_WILLNEED: Call ``madvise()`` for the region with MADV_WILLNEED.
> * @DAMOS_COLD: Call ``madvise()`` for the region with MADV_COLD.
> - * @DAMOS_PAGEOUT: Call ``madvise()`` for the region with MADV_PAGEOUT.
> + * @DAMOS_PAGEOUT: Reclaim the region.
Nice!
> * @DAMOS_HUGEPAGE: Call ``madvise()`` for the region with MADV_HUGEPAGE.
> * @DAMOS_NOHUGEPAGE: Call ``madvise()`` for the region with MADV_NOHUGEPAGE.
> * @DAMOS_LRU_PRIO: Prioritize the region on its LRU lists.
> @@ -146,8 +146,8 @@ struct damon_access_report {
> * The support of each action is up to running &struct damon_operations.
> * &enum DAMON_OPS_VADDR and &enum DAMON_OPS_FVADDR supports all actions except
> * &enum DAMOS_LRU_PRIO and &enum DAMOS_LRU_DEPRIO. &enum DAMON_OPS_PADDR
> - * supports only &enum DAMOS_PAGEOUT, &enum DAMOS_LRU_PRIO, &enum
> - * DAMOS_LRU_DEPRIO, and &DAMOS_STAT.
> + * supports all actions except &enum DAMOS_WILLNEED, &enum DAMOS_COLD,
> + * &enum DAMOS_HUGEPAGE, &enum DAMOS_NOHUGEPAGE.
Thank you for updating this!
But, now I find this place is having outdated information that partially
duplicated with the DAMON design document[2]. I think the design document is
better to maintain this kind of details. What about keeping the high level
information but giving a reference to the documentation for details, for
example, like below?
@@ -143,11 +143,9 @@ struct damon_access_report {
* @DAMOS_STAT: Do nothing but count the stat.
* @NR_DAMOS_ACTIONS: Total number of DAMOS actions
*
- * The support of each action is up to running &struct damon_operations.
- * &enum DAMON_OPS_VADDR and &enum DAMON_OPS_FVADDR supports all actions except
- * &enum DAMOS_LRU_PRIO and &enum DAMOS_LRU_DEPRIO. &enum DAMON_OPS_PADDR
- * supports only &enum DAMOS_PAGEOUT, &enum DAMOS_LRU_PRIO, &enum
- * DAMOS_LRU_DEPRIO, and &DAMOS_STAT.
+ * The support of each action is up to running &struct damon_operations. Refer
+ * to 'Operation Action' section of Documentation/mm/damon/design.rst for
+ * status of the supports.
*/
Thanks,
SJ
[1] https://origin.kernel.org/doc/html/next/mm/damon/maintainer-profile.html#scm-trees
[2] https://origin.kernel.org/doc/html/next/mm/damon/design.html#operation-action
next prev parent reply other threads:[~2025-07-31 17:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 13:22 [PATCH] mm/damon: update expired description of damos_action Sang-Heon Jeon
2025-07-31 17:58 ` SeongJae Park [this message]
2025-08-01 11:35 ` Honggyu Kim
2025-08-01 16:11 ` Sang-Heon Jeon
2025-08-01 16:50 ` SeongJae Park
2025-08-03 2:03 ` Honggyu Kim
2025-08-03 4:22 ` SeongJae Park
2025-08-03 4:43 ` Honggyu Kim
2025-08-03 5:30 ` SeongJae Park
2025-08-03 5:41 ` Honggyu Kim
2025-08-03 13:22 ` Sang-Heon Jeon
2025-08-03 17:42 ` SeongJae Park
2025-08-04 12:56 ` Sang-Heon Jeon
2025-08-05 2:07 ` Honggyu Kim
2025-08-01 15:34 ` Sang-Heon Jeon
2025-08-01 17:02 ` SeongJae Park
2025-08-03 12:44 ` Sang-Heon Jeon
2025-08-03 17:44 ` 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=20250731175827.16060-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=damon@lists.linux.dev \
--cc=ekffu200098@gmail.com \
--cc=honggyu.kim@sk.com \
--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;
as well as URLs for NNTP newsgroup(s).