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 PATCH] mm/damon: introduce damos_sort_type for re-ordering regions list
Date: Wed, 5 Aug 2026 06:51:23 -0700 [thread overview]
Message-ID: <20260805135124.88619-1-sj@kernel.org> (raw)
In-Reply-To: <20260805081246.39417-1-aethernet65535@gmail.com>
On Wed, 5 Aug 2026 16:12:46 +0800 Liew Rui Yan <aethernet65535@gmail.com> wrote:
> Hi SJ,
>
> First of all, I apologize for the noise, and I will drop this patch.
> Secondly, thank you for pointing this out, it made me realize that I was
> fixing a non-existent problem.
No worry, it was good to discuss the idea together!
>
> On Tue, 4 Aug 2026 06:58:33 -0700 SJ Park <sj@kernel.org> wrote:
>
> > The recommended way is setting the min_age naive, and auto-tune it using DAMOS
> > quota or aim-oriented quota auto-tuning. Have you considered using that?
>
> > This sounds like very similar to DAMOS quota's regions prioritizing mechanism.
> > Have you considered using DAMOS quota? If so, could you please add why
> > proposing this new mechanism, with some comparisons?
>
> Yes, I have. And you are right; the existing mechanism is better. I
> wrote this patch because I misunderstood quota.min_score and did not
> even check the implementation of damos_adjust_quota().
Thank you for transparently clarifying these details, Liew. This is very
helpful at conversations.
>
> Whether when implementing dama [1] or this damos_sort_type, I failed to
> realize that min_age might not be such an important parameter on a
> long-running system, and there is really no need to introduce
> auto-tuning or a new mechanism for it.
>
> > I to be honest feel this is too much for "just guess" based patch. I'd like to
> > get clear reasoning of the change and/or test results before reviewing the
> > code. So I'm holding the code review until the high level discussion is done.
>
> Moving forward, I will ensure I am not "reinventing the wheel" or
> "fixing non-existent problem".
I appreciate that. That will be super helpful. But I understand we are human
that cannot "ensure" everything always. Please try not to spend too much time
on unnecessary thing. But don't be scared at making some mistakes, because we
learn from mistakes.
>
> Thank you again for pointing this out. In the future contributions, I
> will try my best to avoid spending time fixing problems that do not
> actually exist.
Sounds nice. And feel free to ask questions or help.
>
> [1] https://lore.kernel.org/damon/20260628085155.20828-1-aethernet65535@gmail.com
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-08-05 13:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260804100719.116538-1-aethernet65535@gmail.com>
2026-08-04 13:58 ` [RFC PATCH] mm/damon: introduce damos_sort_type for re-ordering regions list SJ Park
2026-08-05 8:12 ` Liew Rui Yan
2026-08-05 13:51 ` SJ Park [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=20260805135124.88619-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