mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Nico Pache <npache@redhat.com>
Cc: akpm@linux-foundation.org, hughd@google.com, david@redhat.com,
	lorenzo.stoakes@oracle.com, Liam.Howlett@oracle.com,
	ryan.roberts@arm.com, dev.jain@arm.com, ziy@nvidia.com,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] mm: huge_memory: disallow hugepages if the system-wide THP sysfs settings are disabled
Date: Mon, 9 Jun 2025 14:36:01 +0800	[thread overview]
Message-ID: <a862f31a-bf85-46fe-aebb-ae8c78e5a983@linux.alibaba.com> (raw)
In-Reply-To: <CAA1CXcDgm4EK5sAs6eFa0RiJHaO=H4vCLMKfjZe_GCXvP+c=xw@mail.gmail.com>



On 2025/6/9 02:37, Nico Pache wrote:
> On Thu, Jun 5, 2025 at 2:01 AM Baolin Wang
> <baolin.wang@linux.alibaba.com> wrote:
>>
>> 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.
>>
>> Another rule for madvise, referring to David's suggestion: “allowing for collapsing
>> in a VM without VM_HUGEPAGE in the "madvise" mode would be fine".
>>
>> To address this issue, should check whether the Anon THP configuration is disabled
>> in thp_vma_allowable_orders(), even when the TVA_ENFORCE_SYSFS flag is set.
>>
>> In summary, the current strategy is:
>>
>> 1. If always & orders == 0, and madvise & orders == 0, and hugepage_global_enabled() == false
>> (global THP settings are not enabled), it means mTHP of that orders are prohibited
>> from being used, then madvise_collapse() is forbidden for that orders.
>>
>> 2. If always & orders == 0, and madvise & orders == 0, and hugepage_global_enabled() == true
>> (global THP settings are enabled), and inherit & orders == 0, it means mTHP of that
>> orders are still prohibited from being used, thus madvise_collapse() is not allowed
>> for that orders.
>>
>> Reviewed-by: Zi Yan <ziy@nvidia.com>
>> Signed-off-by: Baolin Wang <baolin.wang@linux.alibaba.com>
>> ---
>>   include/linux/huge_mm.h | 23 +++++++++++++++++++----
>>   1 file changed, 19 insertions(+), 4 deletions(-)
>>
>> diff --git a/include/linux/huge_mm.h b/include/linux/huge_mm.h
>> index 2f190c90192d..199ddc9f04a1 100644
>> --- a/include/linux/huge_mm.h
>> +++ b/include/linux/huge_mm.h
>> @@ -287,20 +287,35 @@ unsigned long thp_vma_allowable_orders(struct vm_area_struct *vma,
>>                                         unsigned long orders)
>>   {
>>          /* Optimization to check if required orders are enabled early. */
>> -       if ((tva_flags & TVA_ENFORCE_SYSFS) && vma_is_anonymous(vma)) {
>> -               unsigned long mask = READ_ONCE(huge_anon_orders_always);
>> +       if (vma_is_anonymous(vma)) {
>> +               unsigned long always = READ_ONCE(huge_anon_orders_always);
>> +               unsigned long madvise = READ_ONCE(huge_anon_orders_madvise);
>> +               unsigned long inherit = READ_ONCE(huge_anon_orders_inherit);
>> +               unsigned long mask = always | madvise;
>> +
>> +               /*
>> +                * If the system-wide THP/mTHP sysfs settings are disabled,
>> +                * then we should never allow hugepages.
>> +                */
>> +               if (!(mask & orders) && !(hugepage_global_enabled() && (inherit & orders)))
>> +                       return 0;
> Hi Baolin,
> 
> Thanks for making this change so we enforce the 'never' being never
> rule. As others have noted, this statement is hard to read-- is there
> any improvements we can make to the readability as Lorenzo suggested?

Yes, will do in next version.

> Either way, I've tested this and the functionality works as intended.
> 
> Tested-by: Nico Pache <npache@redhat.com>

Thanks for testing.

  reply	other threads:[~2025-06-09  6:36 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-05  8:00 [PATCH v2 0/2] fix MADV_COLLAPSE issue if THP " Baolin Wang
2025-06-05  8:00 ` [PATCH v2 1/2] mm: huge_memory: disallow hugepages if the system-wide THP sysfs " Baolin Wang
2025-06-06 16:49   ` Dev Jain
2025-06-06 18:47     ` Dev Jain
2025-06-09  5:57       ` Baolin Wang
2025-06-07 11:55   ` Lorenzo Stoakes
2025-06-07 12:21     ` Lorenzo Stoakes
2025-06-09  6:18       ` Baolin Wang
2025-06-09 15:12         ` Lorenzo Stoakes
2025-06-09  6:10     ` Baolin Wang
2025-06-09 15:17       ` Lorenzo Stoakes
2025-06-11  6:59         ` Baolin Wang
2025-06-08 18:37   ` Nico Pache
2025-06-09  6:36     ` Baolin Wang [this message]
2025-06-11 12:34   ` David Hildenbrand
2025-06-12  7:51     ` Baolin Wang
2025-06-12  8:46       ` Dev Jain
2025-06-12  8:52         ` David Hildenbrand
2025-06-12  8:51       ` David Hildenbrand
2025-06-12 12:45         ` Baolin Wang
2025-06-12 13:05           ` David Hildenbrand
2025-06-12 13:25             ` Baolin Wang
2025-06-12 13:40               ` Baolin Wang
2025-06-12 13:27             ` Lorenzo Stoakes
2025-06-12 13:29               ` Lorenzo Stoakes
2025-06-12 14:13                 ` Baolin Wang
2025-06-12 14:16                   ` David Hildenbrand
2025-06-12 14:20                   ` Lorenzo Stoakes
2025-06-12 14:09               ` David Hildenbrand
2025-06-12 14:49                 ` Lorenzo Stoakes
2025-06-13  2:07                   ` Baolin Wang
2025-06-13  5:18                     ` Lorenzo Stoakes
2025-06-12 13:07         ` Lorenzo Stoakes
2025-06-12 13:13           ` David Hildenbrand
2025-06-12 13:31             ` Lorenzo Stoakes
2025-06-05  8:00 ` [PATCH v2 2/2] mm: shmem: disallow hugepages if the system-wide shmem " Baolin Wang
2025-06-07 12:14   ` Lorenzo Stoakes
2025-06-07 12:17     ` Lorenzo Stoakes
2025-06-09  6:34       ` Baolin Wang
2025-06-09 19:30         ` Lorenzo Stoakes
2025-06-09  6:31     ` Baolin Wang
2025-06-09 15:33       ` Lorenzo Stoakes
2025-06-11  7:02         ` Baolin Wang
2025-06-07 12:28 ` [PATCH v2 0/2] fix MADV_COLLAPSE issue if THP " Lorenzo Stoakes
2025-06-11  7:05   ` Baolin Wang
2025-06-13 14:23 ` Usama Arif
2025-06-13 14:29   ` Lorenzo Stoakes
2025-06-13 14:39     ` Usama Arif
2025-06-13 14:42       ` Lorenzo Stoakes

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=a862f31a-bf85-46fe-aebb-ae8c78e5a983@linux.alibaba.com \
    --to=baolin.wang@linux.alibaba.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.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®