From: Zi Yan <ziy@nvidia.com>
To: Luiz Capitulino <luizcap@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
david@kernel.org, baolin.wang@linux.alibaba.com,
ryan.roberts@arm.com, akpm@linux-foundation.org,
lorenzo.stoakes@oracle.com
Subject: Re: [PATCH v3 09/10] mm: thp: always enable mTHP support
Date: Thu, 09 Apr 2026 16:10:16 -0400 [thread overview]
Message-ID: <3B2D36D9-4B04-4548-ABA0-AE5DAF66B2EF@nvidia.com> (raw)
In-Reply-To: <7830cda5-b3df-4da1-805b-278d5af6b2b1@redhat.com>
On 9 Apr 2026, at 16:07, Luiz Capitulino wrote:
> On 2026-04-09 11:55, Zi Yan wrote:
>> On 8 Apr 2026, at 16:23, Luiz Capitulino wrote:
>>
>>> If PMD-sized pages are not supported on an architecture (ie. the
>>> arch implements arch_has_pmd_leaves() and it returns false) then the
>>> current code disables all THP, including mTHP.
>>>
>>> This commit fixes this by allowing mTHP to be always enabled for all
>>> archs. When PMD-sized pages are not supported, its sysfs entry won't be
>>> created and their mapping will be disallowed at page-fault time.
>>>
>>> Similarly, this commit implements the following changes for shmem:
>>>
>>> - In shmem_allowable_huge_orders(): drop the pgtable_has_pmd_leaves()
>>> check so that mTHP sizes are considered
>>> - In shmem_alloc_and_add_folio(): don't consider PMD and PUD orders
>>> when PMD-sized pages are not supported by the CPU
>>>
>>> Signed-off-by: Luiz Capitulino <luizcap@redhat.com>
>>> ---
>>> mm/huge_memory.c | 13 ++++++++-----
>>> mm/shmem.c | 4 +++-
>>> 2 files changed, 11 insertions(+), 6 deletions(-)
>>>
>>> diff --git a/mm/huge_memory.c b/mm/huge_memory.c
>>> index 86e489c0a150..6de3d8ebc35c 100644
>>> --- a/mm/huge_memory.c
>>> +++ b/mm/huge_memory.c
>>> @@ -118,6 +118,9 @@ unsigned long __thp_vma_allowable_orders(struct vm_area_struct *vma,
>>> else
>>> supported_orders = THP_ORDERS_ALL_FILE_DEFAULT;
>>>
>>> + if (!pgtable_has_pmd_leaves())
>>> + supported_orders &= ~(BIT(PMD_ORDER) | BIT(PUD_ORDER));
>>
>> Why is BIT(PUD_ORDER) also removed? I thought PMD THP support and PUD THP support
>> are separate. Here the code implies PUD THP relies on PMD THP. Is that the case?
>
> This was a suggestion from David to an earlier version:
>
> https://lore.kernel.org/linux-mm/dac20466-adac-4e47-8f50-87f4774fd57b@kernel.org/
>
> My understanding was that if an arch doesn't support PMD pages then it
> probably doesn't support PUD pages either.
Got it. Can you add a comment on “No PMD leaves -> No PUD leaves” for
pgtable_has_pmd_leaves(), so that no one would ask the same question again?
Thanks.
Best Regards,
Yan, Zi
next prev parent reply other threads:[~2026-04-09 20:10 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 20:22 [PATCH v3 00/10] " Luiz Capitulino
2026-04-08 20:22 ` [PATCH v3 01/10] docs: tmpfs: remove implementation detail reference Luiz Capitulino
2026-04-09 15:11 ` Zi Yan
2026-04-08 20:22 ` [PATCH v3 02/10] mm: introduce pgtable_has_pmd_leaves() Luiz Capitulino
2026-04-09 12:26 ` Lance Yang
2026-04-09 18:22 ` Luiz Capitulino
2026-04-08 20:22 ` [PATCH v3 03/10] drivers: dax: use pgtable_has_pmd_leaves() Luiz Capitulino
2026-04-08 20:22 ` [PATCH v3 04/10] drivers: nvdimm: " Luiz Capitulino
2026-04-09 15:21 ` Zi Yan
2026-04-09 18:51 ` Luiz Capitulino
2026-04-08 20:23 ` [PATCH v3 05/10] mm: debug_vm_pgtable: " Luiz Capitulino
2026-04-09 15:25 ` Zi Yan
2026-04-08 20:23 ` [PATCH v3 06/10] mm: shmem: drop has_transparent_hugepage() usage Luiz Capitulino
2026-04-09 15:26 ` Zi Yan
2026-04-08 20:23 ` [PATCH v3 07/10] treewide: rename has_transparent_hugepage() to arch_has_pmd_leaves() Luiz Capitulino
2026-04-09 15:41 ` Zi Yan
2026-04-09 19:43 ` Luiz Capitulino
2026-04-08 20:23 ` [PATCH v3 08/10] mm: replace thp_disabled_by_hw() with pgtable_has_pmd_leaves() Luiz Capitulino
2026-04-09 15:43 ` Zi Yan
2026-04-08 20:23 ` [PATCH v3 09/10] mm: thp: always enable mTHP support Luiz Capitulino
2026-04-09 15:55 ` Zi Yan
2026-04-09 20:07 ` Luiz Capitulino
2026-04-09 20:10 ` Zi Yan [this message]
2026-04-09 21:19 ` Luiz Capitulino
2026-04-08 20:23 ` [PATCH v3 10/10] mm: thp: x86: cleanup PSE feature bit usage Luiz Capitulino
2026-04-09 15:57 ` Zi Yan
2026-04-09 20:10 ` Dave Hansen
2026-04-09 21:24 ` Luiz Capitulino
2026-04-09 8:29 ` [PATCH v3 00/10] mm: thp: always enable mTHP support Lance Yang
2026-04-09 8:36 ` Lorenzo Stoakes
2026-04-09 18:18 ` Luiz Capitulino
2026-04-09 12:35 ` Lance Yang
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=3B2D36D9-4B04-4548-ABA0-AE5DAF66B2EF@nvidia.com \
--to=ziy@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=luizcap@redhat.com \
--cc=ryan.roberts@arm.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