From: Lian Wang <lianux.mm@gmail.com>
To: SJ Park <sj@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Asier Gutierrez <gutierrez.asier@huawei-partners.com>,
damon@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v4 1/3] mm/damon: Introduce DAMOS_QUOTA_HUGEPAGE auto tuning
Date: Tue, 1 Sep 2026 14:58:35 +0800 [thread overview]
Message-ID: <20260901065847.42869-1-lianux.mm@gmail.com> (raw)
In-Reply-To: <20260831144732.80910-2-sj@kernel.org>
Hi SJ and Asier,
Thanks for working on this and for providing the server results. I have two
questions about what hugepage_mem_bp is intended to represent.
> Introduce DAMOS_QUOTA_HUGEPAGE_MEM_BP auto tuning. Add a new DAMOS quota
> goal metric to measure the amount of huge page consumption to total
> memory consumption ratio.
First, NR_ANON_THPS tracks anonymous PMD mappings, while NR_SHMEM_THPS and
NR_FILE_THPS track PMD-mappable page-cache folios. Therefore, splitting only
an anonymous PMD mapping can change hugepage_mem_bp without physically
splitting the folio. Is the intended metric PMD-mapped memory or physical
large-folio memory? Clarifying this and adding a mapping-only test may help.
Second, the metric is global while a DAMOS scheme can target one process.
THPs from other processes or NUMA nodes can satisfy the target or dilute the
monitored process's changes. Is this intentional? If so, documenting the
scope and testing a background THP workload may be useful.
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.
If I have misunderstood any of this, please feel free to ignore these
comments and correct me.
The enum, quota-goal wiring and sysfs exposure otherwise look consistent with
the existing DAMOS autotuning framework. I consider the points above
follow-up questions about semantics and evaluation, rather than blockers for
this series.
For the series:
Reviewed-by: Lian Wang <lianux.mm@gmail.com>
Please feel free to Cc me on related follow-up patches. I am happy to help
review the code. Besides my own DAMON work, I have recently been reviewing
and learning from other DAMON and MM work, and I would be glad to continue.
Thanks,
Lian
Sent using hkml (https://github.com/sjp38/hackermail)
next prev parent reply other threads:[~2026-09-01 6:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 14:47 [PATCH v4 0/3] mm/damon: Introduce a huge page collapsing mechanism using auto tuning SJ Park
2026-08-31 14:47 ` [PATCH v4 1/3] mm/damon: Introduce DAMOS_QUOTA_HUGEPAGE " SJ Park
2026-08-31 18:16 ` sashiko-bot
2026-09-01 0:45 ` SJ Park
2026-09-01 6:58 ` Lian Wang [this message]
2026-09-01 14:23 ` SJ Park
2026-09-02 1:56 ` Lian Wang
2026-09-02 4:23 ` SJ Park
2026-09-02 15:03 ` Gutierrez Asier
2026-09-02 15:15 ` SJ Park
2026-08-31 14:47 ` [PATCH v4 2/3] mm/damon/sysfs: support hugepage_mem_bp quota goal metric SJ Park
2026-08-31 18:22 ` sashiko-bot
2026-09-01 0:46 ` SJ Park
2026-08-31 14:47 ` [PATCH v4 3/3] Docs/mm/damon/design: Document hugepage_mem_bp target metric SJ Park
2026-08-31 15:45 ` Randy Dunlap
2026-08-31 20:00 ` Randy Dunlap
2026-09-01 0:47 ` SJ Park
2026-09-01 5:20 ` Gutierrez Asier
2026-09-01 5:31 ` SJ Park
2026-08-31 18:35 ` sashiko-bot
2026-09-01 0:48 ` SJ Park
2026-09-01 0:49 ` [PATCH v4 0/3] mm/damon: Introduce a huge page collapsing mechanism using auto tuning 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=20260901065847.42869-1-lianux.mm@gmail.com \
--to=lianux.mm@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=gutierrez.asier@huawei-partners.com \
--cc=linux-kernel@vger.kernel.org \
--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