From: David Hildenbrand <david@redhat.com>
To: Dev Jain <dev.jain@arm.com>, akpm@linux-foundation.org
Cc: ryan.roberts@arm.com, willy@infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, catalin.marinas@arm.com,
will@kernel.org, Liam.Howlett@oracle.com,
lorenzo.stoakes@oracle.com, vbabka@suse.cz, jannh@google.com,
anshuman.khandual@arm.com, peterx@redhat.com, joey.gouly@arm.com,
ioworker0@gmail.com, baohua@kernel.org, kevin.brodsky@arm.com,
quic_zhenhuah@quicinc.com, christophe.leroy@csgroup.eu,
yangyicong@hisilicon.com, linux-arm-kernel@lists.infradead.org,
hughd@google.com, yang@os.amperecomputing.com, ziy@nvidia.com
Subject: Re: [PATCH v3 1/5] mm: Optimize mprotect() by batch-skipping PTEs
Date: Thu, 22 May 2025 09:13:32 +0200 [thread overview]
Message-ID: <25c0c700-656c-4a8a-8ef1-5093581cf25c@redhat.com> (raw)
In-Reply-To: <76afb4f3-79b5-4126-b408-614bb6202526@arm.com>
>> ... likely with a better function name,
>
>
> I want to be able to reuse the folio from vm_normal_folio(), and we also
> need
>
> nr_ptes to know how much to skip, so if there is no objection in passing
> int *nr_ptes,
>
> or struct folio **foliop to this new function, then I'll carry on with
> your suggestion :)
Can you quickly prototype what you have in mind and paste it here? Will
make it easier :)
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-05-22 7:13 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 7:48 [PATCH v3 0/5] Optimize mprotect() for large folios Dev Jain
2025-05-19 7:48 ` [PATCH v3 1/5] mm: Optimize mprotect() by batch-skipping PTEs Dev Jain
2025-05-21 8:43 ` Ryan Roberts
2025-05-21 11:58 ` Ryan Roberts
2025-05-22 5:45 ` Dev Jain
2025-05-21 12:06 ` David Hildenbrand
2025-05-22 5:43 ` Dev Jain
2025-05-22 7:13 ` David Hildenbrand [this message]
2025-05-22 7:47 ` Dev Jain
2025-05-22 16:18 ` David Hildenbrand
2025-06-04 10:38 ` Dev Jain
2025-06-04 11:44 ` David Hildenbrand
2025-05-19 7:48 ` [PATCH v3 2/5] mm: Add batched versions of ptep_modify_prot_start/commit Dev Jain
2025-05-21 11:16 ` Ryan Roberts
2025-05-21 11:45 ` Ryan Roberts
2025-05-22 6:33 ` Dev Jain
2025-05-22 7:51 ` Ryan Roberts
2025-05-22 6:39 ` Dev Jain
2025-06-16 6:37 ` Dev Jain
2025-05-19 7:48 ` [PATCH v3 3/5] mm: Optimize mprotect() by PTE batching Dev Jain
2025-05-19 8:18 ` Barry Song
2025-05-20 9:18 ` Dev Jain
2025-05-21 13:26 ` Ryan Roberts
2025-05-22 6:59 ` Dev Jain
2025-05-22 7:11 ` Dev Jain
2025-06-16 11:24 ` Dev Jain
2025-06-26 8:09 ` Ryan Roberts
2025-06-27 4:55 ` Dev Jain
2025-05-19 7:48 ` [PATCH v3 4/5] arm64: Add batched version of ptep_modify_prot_start Dev Jain
2025-05-21 14:14 ` Ryan Roberts
2025-05-22 7:13 ` Dev Jain
2025-05-19 7:48 ` [PATCH v3 5/5] arm64: Add batched version of ptep_modify_prot_commit Dev Jain
2025-05-21 14:17 ` Ryan Roberts
2025-05-22 7:12 ` Dev Jain
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=25c0c700-656c-4a8a-8ef1-5093581cf25c@redhat.com \
--to=david@redhat.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=baohua@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=dev.jain@arm.com \
--cc=hughd@google.com \
--cc=ioworker0@gmail.com \
--cc=jannh@google.com \
--cc=joey.gouly@arm.com \
--cc=kevin.brodsky@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=peterx@redhat.com \
--cc=quic_zhenhuah@quicinc.com \
--cc=ryan.roberts@arm.com \
--cc=vbabka@suse.cz \
--cc=will@kernel.org \
--cc=willy@infradead.org \
--cc=yang@os.amperecomputing.com \
--cc=yangyicong@hisilicon.com \
--cc=ziy@nvidia.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;
as well as URLs for NNTP newsgroup(s).