From: SJ Park <sj@kernel.org>
To: Liew Rui Yan <aethernet65535@gmail.com>
Cc: SJ Park <sj@kernel.org>, damon@lists.linux.dev, linux-mm@kvack.org
Subject: Re: [RFC] mm/damon/damo: saving damon sysfs configuration
Date: Tue, 29 Sep 2026 00:43:00 -0700 [thread overview]
Message-ID: <20260929074300.40012-1-sj@kernel.org> (raw)
In-Reply-To: <20260928191332.138511-1-aethernet65535@gmail.com>
Hi Liew,
On Tue, 29 Sep 2026 03:13:06 +0800 Liew Rui Yan <aethernet65535@gmail.com> wrote:
> Hi SJ and Community,
>
> I've noticed that damo [1] doesn't seem to have a feature for saving
> DAMON SYSFS configuration. I tried 'damo args damon', but it doesn't
> save the DAMOS schemes information.
If so, it is a bug. Could you share more details including how the issue can
be reproduced? Directly sending a PR should also be fine.
> 'damo report damon --json' provides
> more detailed information, but its output cannot be read by 'damo start
> --kdamonds'.
Maybe this is also an issue that we could fix.
>
> I'd like to know if there is currently any way in damo to save the DAMON
> SYSFS configuration that can be correctly read by 'damo start
> --kdamonds'. If not, would it be worth adding one?
I believe it would be useful. Please feel free to send a PR.
Nonetheless, we added the json/yaml kdamonds config support mainly because
there was no good way to flexibly configure kdamonds with the command line
interface. Now it is much more improved [1].
I'd recommend using the command line interface. That is, you could copy your
command line setup in a bash script and modify/reuse it.
Is there a use case that it cannot work or suboptimum?
[1] https://github.com/damonitor/damo/issues/3#issuecomment-5655965736
Thanks,
SJ
[...]
next prev parent reply other threads:[~2026-09-29 7:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 19:13 [RFC] mm/damon/damo: saving damon sysfs configuration Liew Rui Yan
2026-09-29 7:43 ` SJ Park [this message]
2026-09-30 9:58 ` Liew Rui Yan
2026-10-08 12:09 ` Liew Rui Yan
2026-10-08 12:32 ` SJ Park
2026-10-08 13:44 ` Liew Rui Yan
2026-10-08 15:00 ` SJ Park
2026-10-08 16:14 ` Liew Rui Yan
2026-10-09 8:01 ` SJ Park
2026-10-09 12:08 ` Liew Rui Yan
2026-10-09 14:00 ` SJ 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=20260929074300.40012-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=aethernet65535@gmail.com \
--cc=damon@lists.linux.dev \
--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