From: Dev Jain <dev.jain@arm.com>
To: Luke Yang <luyang@redhat.com>
Cc: pfalcato@suse.de, david@kernel.org, surenb@google.com,
jhladky@redhat.com, akpm@linux-foundation.org,
Liam.Howlett@oracle.com, willy@infradead.org, vbabka@suse.cz,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION] mm/mprotect: 2x+ slowdown for >=400KiB regions since PTE batching (cac1db8c3aad)
Date: Wed, 18 Feb 2026 10:20:22 +0530 [thread overview]
Message-ID: <b7ad1462-4672-448a-920d-ace9cef689ab@arm.com> (raw)
In-Reply-To: <aZSoyjQHvVWFBZdZ@luyang-thinkpadp1gen7.toromso.csb>
On 17/02/26 11:13 pm, Luke Yang wrote:
> On Mon, Feb 16, 2026 at 03:42:08PM +0530, Dev Jain wrote:
>> On 13/02/26 10:56 pm, David Hildenbrand (Arm) wrote:
>>> On 2/13/26 18:16, Suren Baghdasaryan wrote:
>>>> On Fri, Feb 13, 2026 at 4:24 PM Pedro Falcato <pfalcato@suse.de> wrote:
>>>>> On Fri, Feb 13, 2026 at 04:47:29PM +0100, David Hildenbrand (Arm) wrote:
>>>>>> Hi!
>>>>>>
>>>>>>
>>>>>> Micro-benchmark results are nice. But what is the real word impact?
>>>>>> IOW, why
>>>>>> should we care?
>>>>> Well, mprotect is widely used in thread spawning, code JITting,
>>>>> and even process startup. And we don't want to pay for a feature we can't
>>>>> even use (on x86).
>>>> I agree. When I straced Android's zygote a while ago, mprotect() came
>>>> up #30 in the list of most frequently used syscalls and one of the
>>>> most used mm-related syscalls due to its use during process creation.
>>>> However, I don't know how often it's used on VMAs of size >=400KiB.
>>> See my point? :) If this is apparently so widespread then finding a real
>>> reproducer is likely not a problem. Otherwise it's just speculation.
>>>
>>> It would also be interesting to know whether the reproducer ran with any
>>> sort of mTHP enabled or not.
>> Yes. Luke, can you experiment with the following microbenchmark:
>>
>> https://pastebin.com/3hNtYirT
>>
>> and see if there is an optimization for pte-mapped 2M folios, before and
>> after the commit?
>>
>> (set transparent_hugepages/enabled=always, hugepages-2048Kb/enabled=always)
> ----------
> amd-epyc2-rome
>
> # before commit
> $ uname -r
> 6.16.0-65.eln150.x86_64
> # after commit
> $ uname -r
> 6.17.0-0.rc1.17.eln150.x86_64
>
> $ cat /sys/kernel/mm/transparent_hugepage/enabled
> [always] madvise never
>
> $ cat /sys/kernel/mm/transparent_hugepage/hugepages-2048kB/enabled
> [always] inherit madvise never
>
> Before commit: Total = 6895988972
> After commit: Total = 2303697782
> Percentage change: -66.6%
>
> ----------
> amd-epyc3-milanx
>
> # before commit
> $ uname -r
> 6.16.0-65.eln150.x86_64
> # after commit
> $ uname -r
> 6.17.0-0.rc1.17.eln150.x86_64
>
> $ cat /sys/kernel/mm/transparent_hugepage/enabled
> [always] madvise never
>
> $ cat /sys/kernel/mm/transparent_hugepage/hugepages-2048kB/enabled
> [always] inherit madvise never
>
> Before commit: Total = 4006750392
> After commit: Total = 1497733191
> Percentage change: -62.6%
> ----------
Thanks. So after all, batching improves stuff :)
>
> Luke
>
next prev parent reply other threads:[~2026-02-18 4:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 15:08 Luke Yang
2026-02-13 15:47 ` David Hildenbrand (Arm)
2026-02-13 16:24 ` Pedro Falcato
2026-02-13 17:16 ` Suren Baghdasaryan
2026-02-13 17:26 ` David Hildenbrand (Arm)
2026-02-16 10:12 ` Dev Jain
2026-02-16 14:56 ` Pedro Falcato
2026-02-17 17:43 ` Luke Yang
2026-02-17 18:08 ` Pedro Falcato
2026-02-18 5:01 ` Dev Jain
2026-02-18 10:06 ` Pedro Falcato
2026-02-18 10:38 ` Dev Jain
2026-02-18 10:46 ` David Hildenbrand (Arm)
2026-02-18 11:58 ` Pedro Falcato
2026-02-18 12:24 ` David Hildenbrand (Arm)
2026-02-19 12:15 ` Pedro Falcato
2026-02-19 13:02 ` David Hildenbrand (Arm)
2026-02-19 15:00 ` Pedro Falcato
2026-02-19 15:29 ` David Hildenbrand (Arm)
2026-02-20 4:12 ` Dev Jain
2026-02-18 11:52 ` Pedro Falcato
2026-02-18 4:50 ` Dev Jain [this message]
2026-02-18 13:29 ` David Hildenbrand (Arm)
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=b7ad1462-4672-448a-920d-ace9cef689ab@arm.com \
--to=dev.jain@arm.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=jhladky@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luyang@redhat.com \
--cc=pfalcato@suse.de \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
/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