From: siddhartha@kenip.in
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Dev Jain <dev.jain@arm.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
mgorman@suse.de
Subject: Re: [PATCH] mm: limit THP alignment – performance gain observed in AI inference workloads
Date: Tue, 01 Jul 2025 19:50:10 +0530 [thread overview]
Message-ID: <9d87a2f8592cdf517e7d501564f42201@kenip.in> (raw)
In-Reply-To: <04a109b1-8f60-45e3-b8d3-70bd849ee877@lucifer.local>
On 2025-07-01 18:58, Lorenzo Stoakes wrote:
> On Tue, Jul 01, 2025 at 06:53:47PM +0530, siddhartha@kenip.in wrote:
>> Hi Lorenzo,
>>
>> Thanks for your clarification, and I appreciate your patience —
>> especially
>> given your role in maintaining and designing the VMA merge logic.
>>
>> I understand now that my earlier phrasing may have repeated your
>> explanation
>> for VMA adjacency, and I regret unintentionally restating it.
>>
>> I’ll make sure to be more careful and direct going forward.
>
> Thanks, no problem. Mostly avoids confusion.
>
>>
>> As for the THP alignment condition now being `IS_ALIGNED(len,
>> PMD_SIZE)`, I
>> agree this resolves the regressions by removing alignment for
>> non-aligned
>> sizes, which was exactly what broke workloads like cactusBSSN or some
>> AI
>> inference loads.
>
> Ack - we're really happy to hear about workloads that this has helped
> as this
> kind of input is very important as to getting insight into how
> THP-related stuff
> impacts real users so we can best optimise especially for workloads
> that are
> very important in the industry right now.
>
>>
>> Thanks again for the guidance — I’m learning a lot from this thread.
>
> Glad to have helped, thanks again for reporting!
>
>>
>> Best Regards,
>> Siddhartha Sharma
>>
>
> Cheers, Lorenzo
Hi Lorenzo,
Thanks for the acknowledgement of my work, I really appreciate it.
Please let me know if there is anything I can do here now moving
forwards with integrating. Furthermore, once integrated and tested, I
would like to see all performance metrics that have seen improvements if
possible.
Best Regards,
Siddhartha Sharma
next prev parent reply other threads:[~2025-07-01 14:20 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
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 [this message]
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=9d87a2f8592cdf517e7d501564f42201@kenip.in \
--to=siddhartha@kenip.in \
--cc=dev.jain@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mgorman@suse.de \
/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