From: Vlastimil Babka <vbabka@suse.cz>
To: Thorsten Leemhuis <regressions@leemhuis.info>,
Rik van Riel <riel@surriel.com>
Cc: Matthias <matthias@bodenbinder.de>,
Andrew Morton <akpm@linux-foundation.org>,
Linux kernel regressions list <regressions@lists.linux.dev>,
LKML <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>,
Yang Shi <yang@os.amperecomputing.com>,
Petr Tesarik <ptesarik@suse.com>
Subject: Re: darktable performance regression on AMD systems caused by "mm: align larger anonymous mappings on THP boundaries"
Date: Thu, 24 Oct 2024 12:23:48 +0200 [thread overview]
Message-ID: <ce35b58e-f18c-4701-8494-fa8d1f6e5148@suse.cz> (raw)
In-Reply-To: <f81ef5bd-e930-4982-a5a8-cd4aca272912@suse.cz>
On 10/24/24 11:58, Vlastimil Babka wrote:
> On 10/24/24 09:45, Thorsten Leemhuis wrote:
>> Hi, Thorsten here, the Linux kernel's regression tracker.
>>
>> Rik, I noticed a report about a regression in bugzilla.kernel.org that
>> appears to be caused by the following change of yours:
>>
>> efa7df3e3bb5da ("mm: align larger anonymous mappings on THP boundaries")
>> [v6.7]
>>
>> It might be one of those "some things got faster, a few things became
>> slower" situations. Not sure. Felt odd that the reporter was able to
>> reproduce it on two AMD systems, but not on a Intel system. Maybe there
>> is a bug somewhere else that was exposed by this.
>
> It seems very similar to what we've seen with spec benchmarks such as cactus
> and bisected to the same commit:
>
> https://bugzilla.suse.com/show_bug.cgi?id=1229012
>
> The exact regression varies per system. Intel regresses too but relatively
> less. The theory is that there are many large-ish allocations that don't
> have individual sizes aligned to 2MB and would have been merged, commit
> efa7df3e3bb5da causes them to become separate areas where each aligns its
> start at 2MB boundary and there are gaps between. This (gaps and vma
> fragmentation) itself is not great, but most of the problem seemed to be
> from the start alignment, which togethter with the access pattern causes
> more TLB or cache missess due to limited associtativity.
>
> So maybe darktable has a similar problem. A simple candidate fix could
> change commit efa7df3e3bb5da so that the mapping size has to be a multiple
> of THP size (2MB) in order to become aligned, right now it's enough if it's
> THP sized or larger.
Maybe this could be enough to fix the issue? (on 6.12-rc4)
diff --git a/mm/mmap.c b/mm/mmap.c
index 9c0fb43064b5..a5297cfb1dfc 100644
--- a/mm/mmap.c
+++ b/mm/mmap.c
@@ -900,7 +900,8 @@ __get_unmapped_area(struct file *file, unsigned long addr, unsigned long len,
if (get_area) {
addr = get_area(file, addr, len, pgoff, flags);
- } else if (IS_ENABLED(CONFIG_TRANSPARENT_HUGEPAGE)) {
+ } else if (IS_ENABLED(CONFIG_TRANSPARENT_HUGEPAGE)
+ && IS_ALIGNED(len, PMD_SIZE)) {
/* Ensures that larger anonymous mappings are THP aligned. */
addr = thp_get_unmapped_area_vmflags(file, addr, len,
pgoff, flags, vm_flags);
next prev parent reply other threads:[~2024-10-24 10:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 7:45 Thorsten Leemhuis
2024-10-24 9:58 ` Vlastimil Babka
2024-10-24 10:23 ` Vlastimil Babka [this message]
2024-10-24 10:49 ` Petr Tesarik
2024-10-24 10:56 ` Vlastimil Babka
2024-10-24 11:13 ` Petr Tesarik
2024-10-24 13:29 ` Vlastimil Babka
2024-10-24 14:14 ` Petr Tesarik
2024-10-24 11:20 ` Matthias Bodenbinder
2024-10-24 15:12 ` [PATCH hotfix 6.12] mm, mmap: limit THP aligment of anonymous mappings to PMD-aligned sizes Vlastimil Babka
2024-10-24 15:47 ` Lorenzo Stoakes
2024-10-24 16:00 ` Lorenzo Stoakes
2024-10-24 16:04 ` Vlastimil Babka
2024-10-24 16:17 ` Lorenzo Stoakes
2024-10-28 13:45 ` Michael Matz
2024-10-24 18:32 ` Yang Shi
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=ce35b58e-f18c-4701-8494-fa8d1f6e5148@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthias@bodenbinder.de \
--cc=ptesarik@suse.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=riel@surriel.com \
--cc=yang@os.amperecomputing.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