From: "Linux regression tracking #adding (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Linux kernel regressions list <regressions@lists.linux.dev>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mm: align larger anonymous mappings on THP boundaries
Date: Sat, 20 Jan 2024 14:43:21 +0100 [thread overview]
Message-ID: <4b26d509-f104-44a9-830c-e00b8496a64a@leemhuis.info> (raw)
In-Reply-To: <d0a136a0-4a31-46bc-adf4-2db109a61672@kernel.org>
On 16.01.24 12:53, Jiri Slaby wrote:
> On 09. 08. 22, 20:24, Rik van Riel wrote:
>> Align larger anonymous memory mappings on THP boundaries by
>> going through thp_get_unmapped_area if THPs are enabled for
>> the current process.
>>
>> With this patch, larger anonymous mappings are now THP aligned.
>> When a malloc library allocates a 2MB or larger arena, that
>> arena can now be mapped with THPs right from the start, which
>> can result in better TLB hit rates and execution time.
>
> This appears to break 32bit processes on x86_64 (at least). In
> particular, 32bit kernel or firefox builds in our build system.
>
> Reverting this on top of 6.7 makes it work again.
>
> Downstream report:
> https://bugzilla.suse.com/show_bug.cgi?id=1218841
> [...]
#regzbot ^introduced efa7df3e3bb5
#regzbot title mm: huge_memory: 32 bit systems or compat
userspace broke
#regzbot link: https://bugzilla.suse.com/show_bug.cgi?id=1218841
#regzbot fix: mm: huge_memory: don't force huge page alignment on 32 bit
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
next prev parent reply other threads:[~2024-01-20 13:43 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 18:24 [PATCH v2] mm: align larger anonymous mappings on THP boundaries Rik van Riel
2022-08-10 17:06 ` Yang Shi
2024-01-16 11:53 ` Jiri Slaby
2024-01-16 12:09 ` Jiri Slaby
2024-01-16 19:16 ` Suren Baghdasaryan
2024-01-16 20:56 ` Yang Shi
2024-01-16 21:57 ` Suren Baghdasaryan
2024-01-16 22:25 ` Yang Shi
2024-01-16 22:30 ` Suren Baghdasaryan
2024-01-16 23:14 ` Yang Shi
2024-01-17 17:40 ` Kees Cook
2024-01-17 23:32 ` Yang Shi
2024-01-18 0:01 ` Suren Baghdasaryan
2024-01-18 0:13 ` Yang Shi
2024-01-18 0:29 ` Suren Baghdasaryan
2024-01-18 1:34 ` Suren Baghdasaryan
2024-01-18 2:10 ` Suren Baghdasaryan
2024-01-16 20:55 ` Yang Shi
2024-01-18 0:07 ` Yang Shi
2024-01-18 0:09 ` Suren Baghdasaryan
2024-01-18 0:11 ` Suren Baghdasaryan
2024-01-18 0:15 ` Yang Shi
2024-01-18 0:28 ` Suren Baghdasaryan
2024-01-18 7:04 ` Jiri Slaby
2024-01-18 17:48 ` Suren Baghdasaryan
2024-01-18 18:42 ` Yang Shi
2024-01-18 18:42 ` Yang Shi
2024-01-20 13:43 ` Linux regression tracking #adding (Thorsten Leemhuis) [this message]
2024-01-20 15:47 ` Linux regression tracking #adding (Thorsten Leemhuis)
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=4b26d509-f104-44a9-830c-e00b8496a64a@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=regressions@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).