Re: [PATCH v3 0/2] mm/mprotect: micro-optimization work

David Hildenbrand (arm)
2026-04-06T09:09:11Z

On 4/6/26 10:29, Pedro Falcato wrote:
> On Thu, Apr 02, 2026 at 11:33:28AM -0700, Andrew Morton wrote:
>> On Thu, 2 Apr 2026 15:16:26 +0100 Pedro Falcato <pfalcato@suse.de> wrote:
>>
>>> Micro-optimize the change_protection functionality and the
>>> change_pte_range() routine. This set of functions works in an incredibly
>>> tight loop, and even small inefficiencies are incredibly evident when spun
>>> hundreds, thousands or hundreds of thousands of times.
>>
>> Thanks, I updated mm.git's mm-unstable branch to this version.
>>
>> The update is rather large. If people think it best to spill this work
>> into next -rc1 then please advise.
>
> I think it's a fairly safe change for 7.1, but I'm biased :) Perhaps others think
> otherwise.

It's mostly code movement, so it should be fine (unless we messed up
passed parameters somehow :) )

--
Cheers,

David