From: SeongJae Park <sj@kernel.org>
To: Gutierrez Asier <gutierrez.asier@huawei-partners.com>
Cc: SeongJae Park <sj@kernel.org>,
artem.kuzin@huawei.com, stepanov.anatoly@huawei.com,
wangkefeng.wang@huawei.com, yanquanmin1@huawei.com,
zuoze1@huawei.com, damon@lists.linux.dev,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v2 0/4] mm/damon: Introduce a huge page collapsing mechanism using auto tuning
Date: Mon, 25 May 2026 09:48:16 -0700 [thread overview]
Message-ID: <20260525164816.8864-1-sj@kernel.org> (raw)
In-Reply-To: <a746583d-af0e-401a-b1f8-d4a0e60d5cc3@huawei-partners.com>
On Mon, 25 May 2026 16:53:17 +0300 Gutierrez Asier <gutierrez.asier@huawei-partners.com> wrote:
> Hi SJ,
>
> On 5/23/2026 8:17 PM, SeongJae Park wrote:
> > On Fri, 22 May 2026 14:55:14 +0000 <gutierrez.asier@huawei-partners.com> wrote:
[...]
> >> A new module is introduced to demonstrate the use of huge pages
> >> collapse autotuning. The goal is to collapse hot regions of a given
> >> process into huge pages. The module launches a kdamond thread for a
> >> certain task provided by the user through monitored_pid module argument.
> >> Hugepage goal autotuning will automatically adjust the aggressiveness
> >> of hot region collapses.
> >
> > Having a module for the demonstration purpose sounds good. But, for the
> > demonstration purpose, as I previousoly commented, making it as a sample module
> > (put under /samples/damon/) or just drop when you drop RFC tag would be better.
> >
> > Let me know if this module is aimed to be as is even after you drop RFC tag.
> I'll move it to samples. I'll keep the RFC in the next version still,
> so I make sure that the major details are polished before I drop RFC tag.
Makes sense. In the case, I think we can further reduce the number of
parameters of the sample module and make the code simpler.
[...]
> >> TODO
> >> ====
> >> - Support page splitting for cold hugepages.
> >
> > Sounds good! By using two DAMOS schemes that doing collapsing and splitting, I
> > think we can make more complete access-aware THP system.
> My thought was to add cold page splitting as a separate RFC in the future.
Makes sense :)
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-05-25 16:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 14:55 [RFC PATCH v2 0/4] mm/damon: Introduce a huge page collapsing mechanism using auto tuning gutierrez.asier
2026-05-22 14:55 ` [RFC PATCH v2 1/4] mm/damon: Generalize ctx_target creation for damon_ops_id and add vaddr support gutierrez.asier
2026-05-23 17:20 ` SeongJae Park
2026-05-22 14:55 ` [RFC PATCH v2 2/4] mm/damon: Introduce DAMOS_QUOTA_HUGEPAGE auto tuning gutierrez.asier
2026-05-23 17:27 ` SeongJae Park
2026-05-25 15:04 ` Gutierrez Asier
2026-05-25 16:51 ` SeongJae Park
2026-05-22 14:55 ` [RFC PATCH v2 3/4] mm/damon: introduce DAMON_HUGEPAGE for hot region hugepage collapsing gutierrez.asier
2026-05-23 17:29 ` SeongJae Park
2026-05-22 14:55 ` [RFC PATCH v2 4/4] Documentation/admin-guide/mm/damon: add DAMON-based Hugepage Management documentation gutierrez.asier
2026-05-23 17:17 ` [RFC PATCH v2 0/4] mm/damon: Introduce a huge page collapsing mechanism using auto tuning SeongJae Park
2026-05-25 13:53 ` Gutierrez Asier
2026-05-25 16:48 ` SeongJae 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=20260525164816.8864-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=artem.kuzin@huawei.com \
--cc=damon@lists.linux.dev \
--cc=gutierrez.asier@huawei-partners.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=stepanov.anatoly@huawei.com \
--cc=wangkefeng.wang@huawei.com \
--cc=yanquanmin1@huawei.com \
--cc=zuoze1@huawei.com \
/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