Re: [PATCH v4 1/3] mm/damon: Introduce DAMOS_QUOTA_HUGEPAGE auto tuning

[SJ Park <sj@kernel.org>]

On Wed, 2 Sep 2026 18:03:39 +0300 Gutierrez Asier <gutierrez.asier@huawei-partners.com> wrote:

> Hi SJ and Lian,
> 
> On 9/1/2026 5:23 PM, SJ Park wrote:
> > Hi Lian,
> > 
> > On Tue,  1 Sep 2026 14:58:35 +0800 Lian Wang <lianux.mm@gmail.com> wrote:
> > 
[...]
> >> Second, the metric is global while a DAMOS scheme can target one process.
> > 
> > Actually it can target multiple processes if those are in single DAMON context.
> > 
> >> THPs from other processes or NUMA nodes can satisfy the target or dilute the
> >> monitored process's changes.  Is this intentional?
> > 
> > I think it is intentional.  The user should have the control on collapsing
> > hugepages, or believe the uncontrolled collapse mechanisms.
> > 
> >> If so, documenting the
> >> scope and testing a background THP workload may be useful.
> > 
> > More documentation and testing are always welcome :)
> > 
> >>
> >> The temporal results approach the 10% and 25% targets, while the consistent
> >> results overshoot the 10% target to about 20% and 45%.  I would describe this
> >> as control-response data.  TPS, latency, TLB, fragmentation and collapse CPU
> >> data could further show the workload benefit and cost.
> > 
> > Yes, those would be helpful.  That's not mandatory for this simple change in my
> > opinion, though.  I would let Asier decide whether and when to make and share
> > such data.
> The idea of this patch was to introduce auto tuning. I think I submitted thebenchmark results when I sent the DAMOS_COLLAPSE feature.
> 
> Anyway, it shouldn't take long for me to get more data. I think it may be useful
> for people to know the actual results in real application.
> 
> SJ, what's the best place to publish all those data? I believe you have more
> experience sharing this data and which platform is the most useful one.>>

I'm never an expert in visibility :)  But if I should recommend, I get three
places off the top of my head.

First, you could simply share the data with plain mail on DAMON and wider
kernel mailing lists like linux-mm@ and linux-kernel@.

Second, if the data is matured, sharing those in conferences like LPC,
OSSummit, FOSDEM or DAMON (nano) Conference would be nice.

Third, if you prefer text, LWN or personal blogs like medias could also be good
places.  I also maintain DAMON porject blog [1].  Kunwu and Lian actually
contributed an article to the blog before.  If you want to submit an article
there, let me know.

[1] https://damonitor.github.io/posts/
[2] https://damonitor.github.io/posts/tlb_flush_policy/


Thanks,
SJ

[...]