From: Pedro Falcato <pfalcato@suse.de>
To: Luke Yang <luyang@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Lorenzo Stoakes <ljs@kernel.org>,
Vlastimil Babka <vbabka@kernel.org>,
Jann Horn <jannh@google.com>,
David Hildenbrand <david@kernel.org>,
Dev Jain <dev.jain@arm.com>,
jhladky@redhat.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Nico Pache <npache@redhat.com>
Subject: Re: [PATCH v2 0/2] mm/mprotect: micro-optimization work
Date: Wed, 1 Apr 2026 15:10:55 +0100 [thread overview]
Message-ID: <vss5mbyhbf756jieb227fh6yu6vvvsggagll3ru4cmlhbbwo25@xv54cwfx7klf> (raw)
In-Reply-To: <CAL2CeBxT4jtJ+LxYb6=BNxNMGinpgD_HYH5gGxOP-45Q2OncqQ@mail.gmail.com>
On Mon, Mar 30, 2026 at 03:55:51PM -0400, Luke Yang wrote:
> Hi Pedro,
>
> Thanks for working on this. I just wanted to share that we've created a
> test kernel with your patches and tested on the following CPUs:
>
> --- aarch64 ---
> Ampere Altra
> Ampere Altra Max
>
> --- x86_64 ---
> AMD EPYC 7713
> AMD EPYC 7351
> AMD EPYC 7542
> AMD EPYC 7573X
> AMD EPYC 7702
> AMD EPYC 9754
> Intel Xeon Gold 6126
> Into Xeon Gold 6330
> Intel Xeon Gold 6530
> Intel Xeon Platinum 8351N
> Intel Core i7-6820HQ
>
> --- ppc64le ---
> IBM Power 10
>
> On average, we see improvements ranging from a minimum of 5% to a
> maximum of 55%, with most improvements showing around a 25% speed up in
> the libmicro/mprot_tw4m micro benchmark.
Nice! Thanks for the tests. I'm wondering, what CPU saw 5% and what CPU
saw 55%? Or was it just inter-run variance?
--
Pedro
next prev parent reply other threads:[~2026-04-01 14:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 15:43 Pedro Falcato
2026-03-24 15:43 ` [PATCH v2 1/2] mm/mprotect: move softleaf code out of the main function Pedro Falcato
2026-03-24 20:12 ` David Hildenbrand (Arm)
2026-03-24 15:43 ` [PATCH v2 2/2] mm/mprotect: special-case small folios when applying write permissions Pedro Falcato
2026-03-24 20:18 ` David Hildenbrand (Arm)
2026-03-25 11:37 ` Pedro Falcato
2026-03-30 15:16 ` David Hildenbrand (Arm)
2026-04-02 0:09 ` Andrew Morton
2026-04-02 3:44 ` Andrew Morton
2026-04-02 7:11 ` David Hildenbrand (Arm)
2026-03-30 19:55 ` [PATCH v2 0/2] mm/mprotect: micro-optimization work Luke Yang
2026-03-30 20:06 ` Andrew Morton
2026-04-01 8:25 ` David Hildenbrand (Arm)
2026-04-01 14:14 ` Pedro Falcato
2026-04-01 14:10 ` Pedro Falcato [this message]
2026-04-02 13:55 ` Luke Yang
2026-04-06 14:32 ` Luke Yang
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=vss5mbyhbf756jieb227fh6yu6vvvsggagll3ru4cmlhbbwo25@xv54cwfx7klf \
--to=pfalcato@suse.de \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=jannh@google.com \
--cc=jhladky@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=luyang@redhat.com \
--cc=npache@redhat.com \
--cc=vbabka@kernel.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