From: "David Hildenbrand (Arm)" <david@kernel.org>
To: "Cédric Le Goater" <clg@redhat.com>,
"Lorenzo Stoakes (ARM)" <ljs@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, Peter Xu <peterx@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>,
Jason Gunthorpe <jgg@nvidia.com>, Zi Yan <ziy@nvidia.com>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/huge_memory: let special huge VMAs bypass the THP policy check
Date: Thu, 6 Aug 2026 18:45:33 +0200 [thread overview]
Message-ID: <857ed4fb-7f99-410f-be1a-59ada04d06a8@kernel.org> (raw)
In-Reply-To: <2a7686ee-56ab-439a-90fd-ad3c10e4c336@redhat.com>
>>
>> +static bool file_vma_honors_thp_toggles(struct vm_area_struct *vma,> +
>> enum tva_type type)
>> +{
>> + const bool forced_collapse = type == TVA_FORCED_COLLAPSE;
>> +
>> + if (forced_collapse)
>> + return false;
>> + /* Huge PFN mappings allocate no folios so the policy doesn't apply. */
>
> So, may be rename the routine to file_vma_thp_policy_applies() ?
Also a possibility. I'll let Lorenzo handle this.
>
>> + return !(vma_test(vma, VMA_PFNMAP_BIT) && vma->vm_ops->huge_fault);
>> +}
>> +
>> +static bool vma_thp_toggles_enabled(struct vm_area_struct *vma,
>
> This routine could use the same 'file_vma_' prefix.
It's true even for non-file vmas.
>
>> + vm_flags_t vm_flags)
>> +{
>> + /* THP=always? */
>> + if (hugepage_global_always())
>> + return true;
>> + /* THP=madvise and actually advised? */
>> + return hugepage_global_enabled() && vm_flags & VM_HUGEPAGE;
>
> I would add extra parentheses around 'vm_flags & VM_HUGEPAGE'
It's even required and the compiler might complain :)
>
>> +}
>> +
>> +static bool file_vma_forces_order_0(struct vm_area_struct *vma,
>> + vm_flags_t vm_flags, enum tva_type type)
>> +{
>> + const bool in_pf = type == TVA_PAGEFAULT;
>> + const bool smaps = type == TVA_SMAPS;
>> +
>> + /*
>> + * Enforce THP collapse requirements as necessary. Anonymous vmas
>> + * were already handled in thp_vma_allowable_orders().
>> + */
>> +
>> + if (file_vma_honors_thp_toggles(vma, type) &&
>> + !vma_thp_toggles_enabled(vma, vm_flags))
>> + return true;
>> +
>> + /*
>> + * Trust that ->huge_fault() handlers know what they are doing
>> + * in fault path.
>> + */
>> + if (((in_pf || smaps)) && vma->vm_ops->huge_fault)
>
> and there remove the extra parentheses.
Agreed, that was already there in existing code.
Anyhow, it was mostly for inspiration for Lorenzo. I should start spelling out
more clearly in the future that this is just a quick prototype, because recently
people assumed that some quick stuff I post inline would be complete or even
tested :)
--
Cheers,
David
next prev parent reply other threads:[~2026-08-06 16:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 5:55 [PATCH] mm/huge_memory: let special huge VMAs bypass the THP policy check Cédric Le Goater
2026-08-05 10:41 ` Lorenzo Stoakes (ARM)
2026-08-05 16:21 ` Cédric Le Goater
2026-08-05 16:26 ` Lorenzo Stoakes (ARM)
2026-08-05 16:29 ` Cédric Le Goater
2026-08-06 1:44 ` Matthew Wilcox
2026-08-06 6:29 ` Lorenzo Stoakes (ARM)
2026-08-06 16:19 ` David Hildenbrand (Arm)
2026-08-06 16:34 ` Cédric Le Goater
2026-08-06 16:45 ` David Hildenbrand (Arm) [this message]
2026-08-05 12:15 ` Jason Gunthorpe
2026-08-05 16:29 ` Lorenzo Stoakes (ARM)
2026-08-05 16:52 ` Jason Gunthorpe
2026-08-05 16:54 ` Lorenzo Stoakes (ARM)
2026-08-06 14:26 ` David Hildenbrand (Arm)
2026-08-06 14:28 ` Lorenzo Stoakes (ARM)
2026-08-06 14:42 ` Cédric Le Goater
2026-08-06 14:47 ` David Hildenbrand (Arm)
2026-08-06 14:53 ` Cédric Le Goater
2026-08-06 14:59 ` David Hildenbrand (Arm)
2026-08-06 16:45 ` Jason Gunthorpe
2026-08-06 16:47 ` David Hildenbrand (Arm)
2026-08-06 16:50 ` AI slop (was Re: [PATCH] mm/huge_memory: let special huge VMAs bypass the THP) " Lorenzo Stoakes (ARM)
2026-08-06 17:05 ` John Hubbard
2026-08-06 17:08 ` Zi Yan
2026-08-06 17:40 ` Gregory Price
2026-08-06 17:42 ` Zi Yan
2026-08-06 17:42 ` Lorenzo Stoakes (ARM)
2026-08-06 19:28 ` Gregory Price
2026-08-06 19:33 ` Lorenzo Stoakes (ARM)
2026-08-06 17:41 ` Lorenzo Stoakes (ARM)
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=857ed4fb-7f99-410f-be1a-59ada04d06a8@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alex.williamson@redhat.com \
--cc=clg@redhat.com \
--cc=jgg@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=peterx@redhat.com \
--cc=stable@vger.kernel.org \
--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