From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Dev Jain <dev.jain@arm.com>
Cc: siddhartha@kenip.in, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, mgorman@suse.de,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [PATCH] mm: limit THP alignment – performance gain observed in AI inference workloads
Date: Mon, 30 Jun 2025 11:54:36 +0100 [thread overview]
Message-ID: <ba2c89bd-88de-48f8-abd0-b62d8b1d50b3@lucifer.local> (raw)
In-Reply-To: <d8ffe547-5516-43e5-9f33-56b2698a0b4f@arm.com>
+cc Vlastimil, please keep him cc'd on discussions here as the author of this
fix in the conversation.
On Mon, Jun 30, 2025 at 10:55:52AM +0530, Dev Jain wrote:
>
>
> For this workload, do you enable mTHPs on your system? My plan is to make a
> similar patch for
>
> the mTHP case and I'd be grateful if you can get me some results : )
I'd urge caution here.
The reason there was a big perf improvement is that, for certain workloads, the
original patch by Rik caused issues with VMA fragmentation. So rather than
getting adjacent VMAs that might later be khugepage'd, you'd get a bunch of VMAs
that were auto-aligned and thus fragmented from one another.
So while you got speed ups on some workloads, you got really bad perf impact on
some that were subject to this.
The observed speed up was on a very specific benchmark also. While it's a great
improvement, it's important to understand the context (see the original patch
for details [0]).
I do think it's worth considering changing thp_get_unmapped_area_vmflags() for
mTHP, as it's currently very limited (just PMD alignment) and it'd possibly be
sensible to change this to checking against allowed THP alignments, but I'd not
assume this is going to get some crazy speed up as observed here.
Note that any such change would probably require some refactoring in THP first
to make it not quite so awful.
I also think for Siddharta's usecase mTHP isn't really relevant is it, as intel
do not support mTHP currently do they?
Regards, Lorenzo
[0]: https://lore.kernel.org/all/20241024151228.101841-2-vbabka@suse.cz/T/#u
next prev parent reply other threads:[~2025-06-30 10:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 10:39 siddhartha
2025-06-27 10:45 ` siddhartha
2025-06-27 15:30 ` Lorenzo Stoakes
2025-06-28 3:49 ` Dev Jain
2025-06-30 0:43 ` siddhartha
2025-06-30 5:25 ` Dev Jain
2025-06-30 5:28 ` Dev Jain
2025-06-30 10:54 ` Lorenzo Stoakes [this message]
2025-06-30 11:48 ` siddhartha
2025-07-01 5:23 ` Dev Jain
2025-07-01 5:28 ` Lorenzo Stoakes
2025-07-01 5:45 ` Dev Jain
2025-07-01 5:53 ` Lorenzo Stoakes
2025-07-01 6:30 ` Dev Jain
2025-07-01 6:50 ` Lorenzo Stoakes
2025-07-01 6:58 ` Dev Jain
2025-07-01 12:15 ` siddhartha
2025-07-01 12:39 ` Lorenzo Stoakes
2025-07-01 13:23 ` siddhartha
2025-07-01 13:28 ` Lorenzo Stoakes
2025-07-01 14:20 ` siddhartha
2025-07-01 16:20 ` Dev Jain
2025-07-01 18:49 ` Zi Yan
2025-07-07 8:56 ` Vlastimil Babka
2025-07-28 5:41 ` siddhartha
2025-07-28 11:00 ` Vlastimil Babka
2025-07-01 15:40 ` Yang Shi
2025-08-11 22:14 siddhartha
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=ba2c89bd-88de-48f8-abd0-b62d8b1d50b3@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=dev.jain@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=siddhartha@kenip.in \
--cc=vbabka@suse.cz \
/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