From: Gutierrez Asier <gutierrez.asier@huawei-partners.com>
To: SeongJae Park <sj@kernel.org>
Cc: <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>, <ljs@kernel.org>,
<Liam.Howlett@oracle.com>, <vbabka@kernel.org>, <rppt@kernel.org>,
<surenb@google.com>, <mhocko@suse.com>, <corbet@lwn.net>,
<skhan@linuxfoundation.org>, <linux-doc@vger.kernel.org>,
<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 1/1] Docs/mm/damon: Document DAMON actions when TRANSPARENT_HUGEPAGE is off
Date: Mon, 16 Mar 2026 17:56:55 +0300 [thread overview]
Message-ID: <224a29a1-13cb-41aa-8736-aebe1023fb7d@huawei-partners.com> (raw)
In-Reply-To: <20260316144848.99972-1-sj@kernel.org>
Hi SJ,
On 3/16/2026 5:48 PM, SeongJae Park wrote:
> Hello Asier,
>
>
> Thank you for sending this patch. :)
>
> On Mon, 16 Mar 2026 14:08:21 +0000 <gutierrez.asier@huawei-partners.com> wrote:
>
>> From: Asier Gutierrez <gutierrez.asier@huawei-partners.com>
>>
>> MADV_HUGEPAGE and MADV_NOHUGEPAGE are guarded and they
>> are not available when compiling the kernel without TRANSPARENT_HUGEPAGE
>> option. The DAMON behaviour is to silently fail[1] in when DAMOS_HUGEPAGE or
>
> checkpatch.pl shows a warning for the above line:
>
> WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
> #12:
> option. The DAMON behaviour is to silently fail[1] in when DAMOS_HUGEPAGE or
Yes, this is due to the link. I tried to keep this patch compact, without a
cover letter. I will submit a new version without the link.
>> DAMOS_NOHUGEPAGE are used, but TRANSPARENT_HUGEPAGE is disabled. Update the
>> DAMON documentation to reflect this behaviour.
>>
>> [1]: https://lore.kernel.org/damon/66131775-180b-4b9f-b7ce-61a3e077b6e6@huawei-partners.com/T/#m278d3c9bbedcceaf2efa51e3dc7b40a40654e51c
>>
>> Signed-off-by: Asier Gutierrez <gutierrez.asier@huawei-partners.com>
>
> Reviewed-by: SeongJae Park <sj@kernel.org>
>
> Andrew might add this to mm.git while fixing the checkpatch warning on his own.
> Let's give time for Andrew today.
>
> I also added this to damon/next tree after fixing the warning. If Andrew
> doesn't pick this with the fix today, I will post mine as v2 of this patch
> tomorrow. If you prefer to do the v2 posting on your own, just let me know :)
>
>
> Thanks,
> SJ
>
> [...]
>
--
Asier Gutierrez
Huawei
next prev parent reply other threads:[~2026-03-16 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 14:08 gutierrez.asier
2026-03-16 14:48 ` SeongJae Park
2026-03-16 14:56 ` Gutierrez Asier [this message]
2026-03-16 15:13 ` SeongJae 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=224a29a1-13cb-41aa-8736-aebe1023fb7d@huawei-partners.com \
--to=gutierrez.asier@huawei-partners.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=artem.kuzin@huawei.com \
--cc=corbet@lwn.net \
--cc=damon@lists.linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=sj@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=stepanov.anatoly@huawei.com \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--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