From: SeongJae Park <sj@kernel.org>
To: Julian Braha <julianbraha@gmail.com>
Cc: SeongJae Park <sj@kernel.org>,
gutierrez.asier@huawei-partners.com, 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: [PATCH v1 2/3] mm/damon: introduce DAMON_HUGEPAGE for hot region hugepage collapsing
Date: Wed, 17 Jun 2026 17:18:41 -0700 [thread overview]
Message-ID: <20260618001842.84103-1-sj@kernel.org> (raw)
In-Reply-To: <39bf837e-d3c3-4b9b-b118-063caadcb700@gmail.com>
On Wed, 17 Jun 2026 17:12:45 +0100 Julian Braha <julianbraha@gmail.com> wrote:
> Hi Asier,
>
> On 6/16/26 16:03, gutierrez.asier@huawei-partners.com wrote:
>
> > +config SAMPLE_DAMON_HPAGE
> > + bool "Build DAMON-based collapse of hot regions (SAMPLE_DAMON_HPAGE)"
> > + depends on DAMON && DAMON_VADDR && TRANSPARENT_HUGEPAGE
> The dependency on DAMON is unnecessary because you already depend on
> DAMON_VADDR.
Nice findiing! There are similar duplicated conditions for other sample
modules, too. If anyone willing to, please feel free to post patches for
cleaning those out.
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-06-18 0:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260616150316.580819-1-gutierrez.asier@huawei-partners.com>
2026-06-17 1:44 ` [PATCH v1 0/3] mm/damon: Introduce a huge page collapsing mechanism using auto tuning SeongJae Park
[not found] ` <20260616150316.580819-3-gutierrez.asier@huawei-partners.com>
2026-06-17 4:04 ` [PATCH v1 2/3] mm/damon: introduce DAMON_HUGEPAGE for hot region hugepage collapsing SeongJae Park
2026-06-18 0:16 ` SeongJae Park
2026-06-18 0:19 ` SeongJae Park
2026-06-17 16:12 ` Julian Braha
2026-06-18 0:18 ` 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=20260618001842.84103-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=julianbraha@gmail.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