From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
David Hildenbrand <david@redhat.com>
Cc: akpm@linux-foundation.org, hughd@google.com,
Liam.Howlett@oracle.com, npache@redhat.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: Fri, 13 Jun 2025 10:07:20 +0800 [thread overview]
Message-ID: <7c911fff-aaf1-430c-89f2-5e7925e90a04@linux.alibaba.com> (raw)
In-Reply-To: <815f383d-8636-490d-8994-486be51f3123@lucifer.local>
On 2025/6/12 22:49, Lorenzo Stoakes wrote:
> On Thu, Jun 12, 2025 at 04:09:27PM +0200, David Hildenbrand wrote:
>>
>>
>>>> @@ -265,6 +265,42 @@ unsigned long __thp_vma_allowable_orders(struct vm_area_struct *vma,
>>>> unsigned long tva_flags,
>>>> unsigned long orders);
>>>> +/* Strictly mask requested anonymous orders according to sysfs settings. */
>>>> +static inline unsigned long __thp_mask_anon_orders(unsigned long vm_flags,
>>>> + unsigned long tva_flags, unsigned long orders)
>>>> +{
>>>> + const unsigned long always = READ_ONCE(huge_anon_orders_always);
>>>> + const unsigned long madvise = READ_ONCE(huge_anon_orders_madvise);
>>>> + const unsigned long inherit = READ_ONCE(huge_anon_orders_inherit);
>>>> + const unsigned long never = ~(always | madvise | inherit);
>>>> +
>>>> + /* Disallow orders that are set to NEVER directly ... */
>>>> + orders &= ~never;
>>>> +
>>>> + /* ... or through inheritance (global == NEVER). */
>>>> + if (!hugepage_global_enabled())
>>>> + orders &= ~inherit;
>>>> +
>>>> + /*
>>>> + * Otherwise, we only enforce sysfs settings if asked. In addition,
>>>> + * if the user sets a sysfs mode of madvise and if TVA_ENFORCE_SYSFS
>>>> + * is not set, we don't bother checking whether the VMA has VM_HUGEPAGE
>>>> + * set.
>>>> + */
>>>> + if (!(tva_flags & TVA_ENFORCE_SYSFS))
>>>> + return orders;
>>>
>>> This implicitly does a & mask as per suggested previous version, which I think
>>> is correct but worth pointing out.
>>
>> Yes.
>>
>>>
>>>> +
>>>> + if (!(vm_flags & VM_HUGEPAGE)) {
>>>
>>> Don't love this sort of mega negation here. I read this as _does_ have huge
>>> page...
>>
>> Well, it's very common to do that, but not objecting to something that is
>> clearer ;)
>>
>> I assume you spotted the
>>
>> if (!(tva_flags & TVA_ENFORCE_SYSFS))
>>
>> :P
>
> Lol yeah I know I know, I just think I guess in this case because you're
> negating elsewhere it makes it harder...
>
>>
>> if (vm_flags & VM_HUGEPAGE)
>> return orders;
>>
>>
>> Would have been easier.
>>
>>>
>>>> + /* Disallow orders that are set to MADVISE directly ... */
>>>> + orders &= ~madvise;
>>>> +
>>>> + /* ... or through inheritance (global == MADVISE). */
>>>> + if (!hugepage_global_always())
>>>> + orders &= ~inherit;
>>>
>>> I hate this implicit 'not hugepage global always so this means either never or
>>> madvise and since we cleared orders for never this means madvise' mental
>>> gymnastics required here.
>>>
>>> Yeah I feel this is a bridge too far, we're getting into double negation and I
>>> think that's more confusiong.
>>
>>
>> Same here ... I think we should just have hugepage_global_madvise(). :)
>
> Ideally in future not have these stupid globals all over the place and rework
> this whole damn thing...
>
>>
>>>
>>>
>>>> + }
>>>
>>> I propose a compromise as I rather like your 'exclude never' negation bit.
>>>
>>> So:
>>>
>>> /* Strictly mask requested anonymous orders according to sysfs settings. */
>>> static inline unsigned long __thp_mask_anon_orders(unsigned long vm_flags,
>>> unsigned long tva_flags, unsigned long orders)
>>> {
>>> const unsigned long always = READ_ONCE(huge_anon_orders_always);
>>> const unsigned long madvise = READ_ONCE(huge_anon_orders_madvise);
>>> const unsigned long inherit = READ_ONCE(huge_anon_orders_inherit);;
>>> const unsigned long never = ~(always | madvise | inherit);
>>> const bool inherit_enabled = hugepage_global_enabled();
>>
>> Can we just have hugepage_global_never/disabled() to use instead?
>
> This would be nice!
>
> Could be a follow up... though again would be nice to somehow do away with all
> this crap altogether.
>
>>
>>>
>>> /* Disallow orders that are set to NEVER directly ... */
>>> orders &= ~never;
>>>
>>> /* ... or through inheritance (global == NEVER). */
>>> if (!inherit_enabled)
>>> orders &= ~inherit;>
>>> /*
>>> * Otherwise, we only enforce sysfs settings if asked. In addition,
>>> * if the user sets a sysfs mode of madvise and if TVA_ENFORCE_SYSFS
>>> * is not set, we don't bother checking whether the VMA has VM_HUGEPAGE
>>> * set.
>>> */
>>> if (!(tva_flags & TVA_ENFORCE_SYSFS))
>>> return orders;
>>>
>>> if (hugepage_global_always())
>>> return orders & (always | inherit);
>>>
>>> /* We already excluded never inherit above. */
>>> if (vm_flags & VM_HUGEPAGE)
>>> return orders & (always | madvise | inherit);
>>>
>>> return orders & always;
>>> }
>>>
>>> What do you think?
>>
>> With the fixup, it would work for me. No magical "mask" variables :D
>
> Thanks!
Fair enough. You both prefer the 'exclude never' logic, and I will
follow that logic.
>>>> + return orders;
>>>> +}
>>>> +
>>>> /**
>>>> * thp_vma_allowable_orders - determine hugepage orders that are allowed for vma
>>>> * @vma: the vm area to check
>>>> @@ -287,16 +323,8 @@ 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 (vm_flags & VM_HUGEPAGE)
>>>> - mask |= READ_ONCE(huge_anon_orders_madvise);
>>>> - if (hugepage_global_always() ||
>>>> - ((vm_flags & VM_HUGEPAGE) && hugepage_global_enabled()))
>>>> - mask |= READ_ONCE(huge_anon_orders_inherit);
>>>> -
>>>> - orders &= mask;
>>>> + if (vma_is_anonymous(vma)) {
>>>> + orders = __thp_mask_anon_orders(vm_flags, tva_flags, orders);
>>>> if (!orders)
>>>> return 0;
>>>
>>> I pointed out to Baolin that __thp_vma_allowable_orders() handles the orders ==
>>> 0 case almost immediately so there's no need to do this, it just makes the code
>>> noisier.
>>
>> The reason we added it in the first place was to not do the (expensive)
>> function call.
>
> Ack point taken!
>
>>
>>
>> --
>> Cheers,
>>
>> David / dhildenb
>>
>
> For convenience, I enclose the fixed version + tweaked the inherit local bool to
> be inherit_never to be clearer:
>
> /* Strictly mask requested anonymous orders according to sysfs settings. */
> static inline unsigned long __thp_mask_anon_orders(unsigned long vm_flags,
> unsigned long tva_flags, unsigned long orders)
> {
> const unsigned long always = READ_ONCE(huge_anon_orders_always);
> const unsigned long madvise = READ_ONCE(huge_anon_orders_madvise);
> const unsigned long inherit = READ_ONCE(huge_anon_orders_inherit);;
> const unsigned long never = ~(always | madvise | inherit);
> const bool inherit_never = !hugepage_global_enabled();
>
> /* Disallow orders that are set to NEVER directly ... */
> orders &= ~never;
>
> /* ... or through inheritance (global == NEVER). */
> if (inherit_never)
> orders &= ~inherit;
>
> /*
> * Otherwise, we only enforce sysfs settings if asked. In addition,
> * if the user sets a sysfs mode of madvise and if TVA_ENFORCE_SYSFS
> * is not set, we don't bother checking whether the VMA has VM_HUGEPAGE
> * set.
> */
> if (!(tva_flags & TVA_ENFORCE_SYSFS))
> return orders;
>
> /* We already excluded never inherit above. */
> if (vm_flags & VM_HUGEPAGE)
> return orders & (always | madvise | inherit);
>
> if (hugepage_global_always())
> return orders & (always | inherit);
>
> return orders & always;
> }
Thanks Lorenzo. Let me follow this logic and do some testing.
next prev parent reply other threads:[~2025-06-13 2:07 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
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 [this message]
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=7c911fff-aaf1-430c-89f2-5e7925e90a04@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®