From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Dev Jain <dev.jain@arm.com>,
akpm@linux-foundation.org, hughd@google.com, david@redhat.com
Cc: ziy@nvidia.com, lorenzo.stoakes@oracle.com,
Liam.Howlett@oracle.com, npache@redhat.com, ryan.roberts@arm.com,
baohua@kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] mm: huge_memory: disallow hugepages if the system-wide THP sysfs settings are disabled
Date: Tue, 24 Jun 2025 17:57:33 +0800 [thread overview]
Message-ID: <e666835e-4c15-4f5a-bab1-f27e0c438f16@linux.alibaba.com> (raw)
In-Reply-To: <8912e179-601a-4677-b2f6-14f40d488d98@arm.com>
On 2025/6/24 16:41, Dev Jain wrote:
>
> On 23/06/25 1:58 pm, Baolin Wang wrote:
>> When invoking thp_vma_allowable_orders(), the TVA_ENFORCE_SYSFS flag
>> is not
>> specified, we will ignore the THP sysfs settings. Whilst it makes
>> sense for the
>> callers who do not specify this flag, it creates a odd and surprising
>> situation
>> where a sysadmin specifying 'never' for all THP sizes still observing
>> THP pages
>> being allocated and used on the system.
>>
>> The motivating case for this is MADV_COLLAPSE. The MADV_COLLAPSE will
>> ignore
>> the system-wide Anon THP sysfs settings, which means that even though
>> we have
>> disabled the Anon THP configuration, MADV_COLLAPSE will still attempt
>> to collapse
>> into a Anon THP. This violates the rule we have agreed upon: never
>> means never.
>>
>> Currently, besides MADV_COLLAPSE not setting TVA_ENFORCE_SYSFS, there
>> is only
>> one other instance where TVA_ENFORCE_SYSFS is not set, which is in the
>> collapse_pte_mapped_thp() function, but I believe this is reasonable
>> from its
>> comments:
>>
>> "
>> /*
>> * If we are here, we've succeeded in replacing all the native pages
>> * in the page cache with a single hugepage. If a mm were to fault-in
>> * this memory (mapped by a suitably aligned VMA), we'd get the hugepage
>> * and map it by a PMD, regardless of sysfs THP settings. As such, let's
>> * analogously elide sysfs THP settings here.
>> */
>> if (!thp_vma_allowable_order(vma, vma->vm_flags, 0, PMD_ORDER))
>
> So the behaviour now is: First check whether THP settings converge to
> never.
> Then, if enforce_sysfs is not set, return immediately. So in this
> khugepaged
> code will it be better to call __thp_vma_allowable_orders()? If the sysfs
> settings are changed to never before hitting collapse_pte_mapped_thp(),
> then right now we will return SCAN_VMA_CHECK from here, whereas, the
> comment
> says "regardless of sysfs THP settings", which should include "regardless
> of whether the sysfs settings say never".
Sounds reasonable to me. Thanks.
I will change thp_vma_allowable_order() to __thp_vma_allowable_orders()
in the collapse_pte_mapped_thp() function to maintain consistency with
the original logic.
Lorenzo and David, how do you think? Thanks.
next prev parent reply other threads:[~2025-06-24 9:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 8:28 [PATCH v3 0/2] fix MADV_COLLAPSE issue if THP " Baolin Wang
2025-06-23 8:28 ` [PATCH v3 1/2] mm: huge_memory: disallow hugepages if the system-wide THP sysfs " Baolin Wang
2025-06-23 10:26 ` Lorenzo Stoakes
2025-06-24 1:45 ` Baolin Wang
2025-06-23 11:08 ` Barry Song
2025-06-24 1:44 ` Baolin Wang
2025-06-23 13:54 ` David Hildenbrand
2025-06-24 1:48 ` Baolin Wang
2025-06-24 8:29 ` David Hildenbrand
2025-06-24 9:20 ` Baolin Wang
2025-06-23 14:39 ` Zi Yan
2025-06-24 8:41 ` Dev Jain
2025-06-24 9:57 ` Baolin Wang [this message]
2025-06-24 14:08 ` Baolin Wang
2025-06-24 14:42 ` Dev Jain
2025-06-23 8:28 ` [PATCH v3 2/2] mm: shmem: disallow hugepages if the system-wide shmem " Baolin Wang
2025-06-23 10:45 ` Lorenzo Stoakes
2025-06-23 13:59 ` David Hildenbrand
2025-06-24 1:52 ` Baolin Wang
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=e666835e-4c15-4f5a-bab1-f27e0c438f16@linux.alibaba.com \
--to=baolin.wang@linux.alibaba.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=david@redhat.com \
--cc=dev.jain@arm.com \
--cc=hughd@google.com \
--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®