From: David Hildenbrand <david@redhat.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Zi Yan <ziy@nvidia.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Nico Pache <npache@redhat.com>,
Ryan Roberts <ryan.roberts@arm.com>, Dev Jain <dev.jain@arm.com>,
Barry Song <baohua@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
linux-mm@kvack.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: update THP documentation to clarify sysfs "never" setting
Date: Tue, 22 Jul 2025 09:59:09 +0200 [thread overview]
Message-ID: <64b5b420-4c2a-423e-825b-b2c309274d71@redhat.com> (raw)
In-Reply-To: <39a75435-5fea-4816-b484-477d400c3564@redhat.com>
On 22.07.25 09:20, David Hildenbrand wrote:
> On 21.07.25 17:55, Lorenzo Stoakes wrote:
>> Rather confusingly, setting all Transparent Huge Page sysfs settings to
>> "never" does not in fact result in THP being globally disabled.
>>
>> Rather, it results in khugepaged being disabled, but one can still obtain
>> THP pages using madvise(..., MADV_COLLAPSE).
>>
>> This is something that has remained poorly documented for some time, and it
>> is likely the received wisdom of most users of THP that never does, in
>> fact, mean never.
>>
>> It is therefore important to highlight, very clearly, that this is not the
>> ase.
>>
>> Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
>> ---
>
> Can we also somehow tone down or clarify the "entirely disabled"?
Ah, missed that you touched that already.
Acked-by: David Hildenbrand <david@redhat.com>
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2025-07-22 7:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 15:55 Lorenzo Stoakes
2025-07-21 16:27 ` SeongJae Park
2025-07-22 1:13 ` Zi Yan
2025-07-22 1:30 ` Baolin Wang
2025-07-22 2:23 ` Barry Song
2025-07-22 2:33 ` Baolin Wang
2025-07-22 3:37 ` Barry Song
2025-07-22 5:29 ` Lorenzo Stoakes
2025-07-23 15:41 ` Lorenzo Stoakes
2025-07-22 5:24 ` Lorenzo Stoakes
2025-07-22 5:25 ` Lorenzo Stoakes
2025-07-22 5:34 ` Lorenzo Stoakes
2025-07-22 5:59 ` Baolin Wang
2025-07-22 8:19 ` Barry Song
2025-07-22 7:20 ` David Hildenbrand
2025-07-22 7:59 ` David Hildenbrand [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=64b5b420-4c2a-423e-825b-b2c309274d71@redhat.com \
--to=david@redhat.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=corbet@lwn.net \
--cc=dev.jain@arm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=npache@redhat.com \
--cc=ryan.roberts@arm.com \
--cc=ziy@nvidia.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
all inboxes | Powered by JetHome®