linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Baolin Wang <baolin.wang@linux.alibaba.com>
Cc: David Hildenbrand <david@redhat.com>,
	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: Thu, 12 Jun 2025 15:20:50 +0100	[thread overview]
Message-ID: <976f8544-91b7-49f7-975f-fac29a00d3fa@lucifer.local> (raw)
In-Reply-To: <519c59e6-20ef-4edf-88b8-a71f38cbd2de@linux.alibaba.com>

On Thu, Jun 12, 2025 at 10:13:40PM +0800, Baolin Wang wrote:
>
>
> On 2025/6/12 21:29, Lorenzo Stoakes wrote:
> > On Thu, Jun 12, 2025 at 02:27:06PM +0100, Lorenzo Stoakes wrote:
> > [snip]
> >
> > > 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();
> > >
> > > 	/* 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);
> >
> > Of course... I immediately made a mistake... swap these two statements around. I
> > thought it'd be 'neater' to do the first one first, but of course it means
> > madvise (rather than inherit) orders don't get selected.
> >
> > This WHOLE THING needs refactoring.
>
> Personally, I think the 'exclude never' logic becomes more complicated. I
> made a simpler change without adding a new helper. What do you think?
>
> static inline
> unsigned long thp_vma_allowable_orders(struct vm_area_struct *vma,
>                                        unsigned long vm_flags,
>                                        unsigned long tva_flags,
>                                        unsigned long orders)
> {
>         /* Optimization to check if required orders are enabled early. */
>         if (vma_is_anonymous(vma)) {

I hate the level of indentation here. There's really no reason not to have this
as a helper as this just solves this problem and any sane compiler will inline.

>                 unsigned long mask = READ_ONCE(huge_anon_orders_always);
>                 bool huge_enforce = !(tva_flags & TVA_ENFORCE_SYSFS);

Huge enforce is when we don't have enforce flag set? This is super confusing.

>                 bool has_madvise =  vm_flags & VM_HUGEPAGE;
>
>                 /*
>                  * 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 (huge_enforce || has_madvise)
>                         mask |= READ_ONCE(huge_anon_orders_madvise);

I find this more confusing, honestly.

I far prefer having the never checks up front, and I prefer David's 'explicitly
deal with never through negations' approach.

I also think adding these READ_ONCE()'s here adds a ton of noise.

>                 if (hugepage_global_always() ||
>                     ((has_madvise || huge_enforce) &&
> hugepage_global_enabled()))

This combination of conditions is just horribly confusing. And why are you
giving an explanation above but not for this one...

This is just combining a ton of logic in a confusing way.

>                         mask |= READ_ONCE(huge_anon_orders_inherit);
>
>                 orders &= mask;
>                 if (!orders)
>                         return 0;
>         }
>
>         return __thp_vma_allowable_orders(vma, vm_flags, tva_flags, orders);
> }

Thanks for the suggestion but I do prefer the proposed compromise solution.

>
> >
> > >
> > > 	return orders & always;
> > > }
> > >
> > > What do you think?
> > >
> > >
> > > > +       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.
> > >
> > > I mean we _could_ keep it but I think it's better not to for cleanliness, what
> > > do you think?
> > >
> > > >          }
> > > >
> > > >
> > > > --
> > > > Cheers,
> > > >
> > > > David / dhildenb
> > > >
> > >


  parent reply	other threads:[~2025-06-12 14:21 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 [this message]
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=976f8544-91b7-49f7-975f-fac29a00d3fa@lucifer.local \
    --to=lorenzo.stoakes@oracle.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=baolin.wang@linux.alibaba.com \
    --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=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