From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: siddhartha@kenip.in
Cc: 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: Fri, 27 Jun 2025 16:30:12 +0100 [thread overview]
Message-ID: <4990838b-660d-46a2-b21c-67adcba61ff9@lucifer.local> (raw)
In-Reply-To: <28338f055b3c9afa8b69ff6f05ea20ed@kenip.in>
+cc Vlata
On Fri, Jun 27, 2025 at 04:09:16PM +0530, siddhartha@kenip.in wrote:
> Hi all,
>
> I wanted to share validation data from a Hugging Face-based AI inferencing
> workload,
> which was significantly impacted by the THP alignment logic introduced in
> commit efa7df3e3bb5.
>
> Using transformer models with dynamic input lengths on Intel Xeon (Cooper
> Lake),
> we observed up to a 3200% throughput improvement after applying the patch
> from Oct 2024:
>
> mm: limit THP alignment of anonymous mappings to PMD-aligned sizes
All congratulations are owed to Vlastimil Babka for doing this, cc'd :)
I gather he enjoys novelty beer mugs as tokens of thanks ;)
>
> Metrics:
> - Model: BERT-base
> - Inference engine: Transformers + ONNX Runtime
> - Kernel: 6.6 vs patched 6.6.8
> - Batch size: 8-32, input length: 64-512 tokens
> - Metric: inference throughput (samples/sec)
>
> Thanks for the fix -- this change had real impact on a production-relevant
> workload.
>
> Best Regards,
> Siddhartha Sharma
> ISV @ Kenip
> Solution Link: https://www.intel.com/content/www/us/en/partner/showcase/offering/a5bHo00000045YUIAY/deadlock-clearance.html
>
next prev parent reply other threads:[~2025-06-27 15:30 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 [this message]
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
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=4990838b-660d-46a2-b21c-67adcba61ff9@lucifer.local \
--to=lorenzo.stoakes@oracle.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