From: Liew Rui Yan <aethernet65535@gmail.com>
To: SJ Park <sj@kernel.org>
Cc: Liew Rui Yan <aethernet65535@gmail.com>,
damon@lists.linux.dev, linux-mm@kvack.org
Subject: Re: [RFC] mm/damon/damo: saving damon sysfs configuration
Date: Sat, 10 Oct 2026 16:14:07 +0800 [thread overview]
Message-ID: <20261010081453.28212-1-aethernet65535@gmail.com> (raw)
In-Reply-To: <20261009140041.11741-1-sj@kernel.org>
On Fri, 09 Oct 2026 07:00:41 -0700 SJ Park <sj@kernel.org> wrote:
> Hi Liew,
>
> On Fri, 9 Oct 2026 20:08:33 +0800 Liew Rui Yan <aethernet65535@gmail.com> wrote:
>
> [...]
> > Yes. My expected behavior is to completely save and restore the DAMON
> > SYSFS configuration, including DAMOS Schemes. But it cannot done by
> > 'damo args damon'.
> >
> > In the script I provided, it first apply lru.json and then uses
> > 'damo args damon' to export the current configuration file.
>
> 'damo args damon' does not export the running DAMON parameters. Why do you
> expect so? Has some document confused you?
Thank you for your clarify.
Actually, there is no any document confused me. 'damo args' section in
USAGE.md is good enough. I think it is just because I made assumption
about what 'damo args damon' would do.
>
> > I expected
> > that reapplying this exported configuration (via 'damo start --kdamonds')
> > would fully restore the previous DAMON SYSFS setup.
>
> So this expectation is wrong.
>
> >
> > However, the current/unexpected behavior is that it drops the DAMOS
> > Schemes configuration entirely. In other words, I cannot fully save
> > and restore the DAMON SYSFS configuration using 'damo args damon'.
>
> So it looks like there is not problem. Please let me know if I'm missing
> something.
I will reduce these kinds of false positive from the next time. At
least, I will state what behavior I expect.
[...]
Best regards,
Rui Yan
prev parent reply other threads:[~2026-10-10 8:14 UTC|newest]
Thread overview: 12+ 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
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
2026-10-10 8:14 ` Liew Rui Yan [this message]
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=20261010081453.28212-1-aethernet65535@gmail.com \
--to=aethernet65535@gmail.com \
--cc=damon@lists.linux.dev \
--cc=linux-mm@kvack.org \
--cc=sj@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