From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Lance Yang <lance.yang@linux.dev>, luizcap@redhat.com
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
david@kernel.org, ziy@nvidia.com, corbet@lwn.net,
tsbogend@alpha.franken.de, maddy@linux.ibm.com,
mpe@ellerman.id.au, agordeev@linux.ibm.com,
gerald.schaefer@linux.ibm.com, hca@linux.ibm.com,
gor@linux.ibm.com, x86@kernel.org, tglx@kernel.org,
mingo@redhat.com, bp@alien8.de, ira.weiny@intel.com,
hughd@google.com, dave.hansen@linux.intel.com, djbw@kernel.org,
vishal.l.verma@intel.com, dave.jiang@intel.com,
akpm@linux-foundation.org, yintirui@huawei.com, ljs@kernel.org
Subject: Re: [PATCH v5 14/14] mm: thp: always enable mTHP support
Date: Wed, 3 Jun 2026 15:23:49 +0800 [thread overview]
Message-ID: <2132b0a3-1085-47cb-95ca-3aaa7f8ed44b@linux.alibaba.com> (raw)
In-Reply-To: <20260603064718.81699-1-lance.yang@linux.dev>
On 6/3/26 2:47 PM, Lance Yang wrote:
> Hi Luiz,
>
> SHMEM_HUGE_FORCE still assumes PMD order in a few places.
>
> Is that expected?
>
> shmem_init() only sets the default inherit mask when PMD leaves are
> available.
>
> if (!shmem_orders_configured && pgtable_has_pmd_leaves())
> huge_shmem_orders_inherit = BIT(HPAGE_PMD_ORDER);
>
> But shmem_parse_huge() rejects "force" unless the mask is exactly PMD
> order.
>
> if (huge == SHMEM_HUGE_FORCE &&
> huge_shmem_orders_inherit != BIT(HPAGE_PMD_ORDER))
> return -EINVAL;
>
> Even if "force" is selected, shmem_huge_global_enabled() still return
> only PMD order.
>
> if (shmem_huge_force || shmem_huge == SHMEM_HUGE_FORCE)
> return maybe_pmd_order;
>
> and shmem_allowable_huge_orders() mask it out.
>
> if (!pgtable_has_pmd_leaves())
> disabled_orders = BIT(PMD_ORDER);
>
> if (!vma || !vma_is_anon_shmem(vma))
> return global_orders & ~disabled_orders;
>
> For anon shmem, it can also return 0 for same reason.
>
> if (shmem_huge == SHMEM_HUGE_FORCE)
> return READ_ONCE(huge_shmem_orders_inherit) & ~disabled_orders;
>
> Should SHMEM_HUGE_FORCE use the available mTHP orders below PMD when
> pgtable_has_pmd_leaves() is false?
No. That's exactly the strategy we agreed on after lots of discussion:
1. The options 'force' and 'deny' are dropped for mTHP interfaces, which
are rather testing artifacts from the old ages.
2. If top level value is 'force', then only PMD-sized hugepages have
enabled="inherit", otherwise configuration will be failed and vice versa.
You can check commit 4b98995530b7 ("mm: shmem: add multi-size THP sysfs
interface for anonymous shmem") for more information.
next prev parent reply other threads:[~2026-06-03 7:24 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 14:55 [PATCH v5 00/14] " Luiz Capitulino
2026-05-29 14:55 ` [PATCH v5 01/14] docs: tmpfs: remove implementation detail reference Luiz Capitulino
2026-06-02 10:16 ` Dev Jain
2026-05-29 14:55 ` [PATCH v5 02/14] mm: shmem: shmem_getattr(): set blksize to highest supported THP order Luiz Capitulino
2026-06-02 15:13 ` Zi Yan
2026-05-29 14:55 ` [PATCH v5 03/14] mm: introduce pgtable_has_pmd_leaves() Luiz Capitulino
2026-05-29 14:55 ` [PATCH v5 04/14] drivers: dax: use pgtable_has_pmd_leaves() Luiz Capitulino
2026-05-29 14:55 ` [PATCH v5 05/14] drivers: nvdimm: " Luiz Capitulino
2026-05-29 14:55 ` [PATCH v5 06/14] mm: debug_vm_pgtable: " Luiz Capitulino
2026-05-29 14:55 ` [PATCH v5 07/14] mm: shmem: allow THP support determination at folio allocation time Luiz Capitulino
2026-06-01 12:09 ` Baolin Wang
2026-06-01 12:20 ` Luiz Capitulino
2026-06-02 2:55 ` Baolin Wang
2026-05-29 14:55 ` [PATCH v5 08/14] s390: move has_transparent_hugepage() out of THP guard Luiz Capitulino
2026-05-29 14:55 ` [PATCH v5 09/14] powerpc: " Luiz Capitulino
2026-05-29 14:55 ` [PATCH v5 10/14] mips: " Luiz Capitulino
2026-05-29 14:55 ` [PATCH v5 11/14] x86: " Luiz Capitulino
2026-05-29 14:55 ` [PATCH v5 12/14] treewide: introduce arch_has_pmd_leaves() Luiz Capitulino
2026-05-29 14:55 ` [PATCH v5 13/14] mm: replace thp_disabled_by_hw() with pgtable_has_pmd_leaves() Luiz Capitulino
2026-05-29 14:55 ` [PATCH v5 14/14] mm: thp: always enable mTHP support Luiz Capitulino
2026-06-01 12:02 ` Baolin Wang
2026-06-02 3:02 ` Baolin Wang
2026-06-03 6:47 ` Lance Yang
2026-06-03 7:23 ` Baolin Wang [this message]
2026-06-03 7:40 ` Lance Yang
2026-06-03 8:12 ` Lance Yang
2026-06-03 17:40 ` Luiz Capitulino
2026-06-04 2:04 ` Lance Yang
2026-06-11 18:00 ` [PATCH v5 00/14] " Luiz Capitulino
2026-06-11 18:21 ` Andrew Morton
2026-06-11 18:27 ` Luiz Capitulino
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=2132b0a3-1085-47cb-95ca-3aaa7f8ed44b@linux.alibaba.com \
--to=baolin.wang@linux.alibaba.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=dave.jiang@intel.com \
--cc=david@kernel.org \
--cc=djbw@kernel.org \
--cc=gerald.schaefer@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=hughd@google.com \
--cc=ira.weiny@intel.com \
--cc=lance.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=luizcap@redhat.com \
--cc=maddy@linux.ibm.com \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=tglx@kernel.org \
--cc=tsbogend@alpha.franken.de \
--cc=vishal.l.verma@intel.com \
--cc=x86@kernel.org \
--cc=yintirui@huawei.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