linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Davidlohr Bueso <dave@stgolabs.net>
To: Pedro Falcato <pfalcato@suse.de>
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>,
	Luke Yang <luyang@redhat.com>,
	jhladky@redhat.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] mm/mprotect: special-case small folios when applying write permissions
Date: Mon, 6 Apr 2026 17:50:26 -0700	[thread overview]
Message-ID: <20260407005026.ytf7ed4bk2ljyflx@offworld> (raw)
In-Reply-To: <20260402141628.3367596-3-pfalcato@suse.de>

On Thu, 02 Apr 2026, Pedro Falcato wrote:

>@@ -334,34 +371,20 @@ static long change_pte_range(struct mmu_gather *tlb,
>
> 			nr_ptes = mprotect_folio_pte_batch(folio, pte, oldpte, max_nr_ptes, flags);
>
>-			oldpte = modify_prot_start_ptes(vma, addr, pte, nr_ptes);
>-			ptent = pte_modify(oldpte, newprot);
>-
>-			if (uffd_wp)
>-				ptent = pte_mkuffd_wp(ptent);
>-			else if (uffd_wp_resolve)
>-				ptent = pte_clear_uffd_wp(ptent);
>-
> 			/*
>-			 * In some writable, shared mappings, we might want
>-			 * to catch actual write access -- see
>-			 * vma_wants_writenotify().
>-			 *
>-			 * In all writable, private mappings, we have to
>-			 * properly handle COW.
>-			 *
>-			 * In both cases, we can sometimes still change PTEs
>-			 * writable and avoid the write-fault handler, for
>-			 * example, if a PTE is already dirty and no other
>-			 * COW or special handling is required.
>+			 * Optimize for the small-folio common case by
>+			 * special-casing it here. Compiler constant propagation
>+			 * plus copious amounts of __always_inline does wonders.
> 			 */
>-			if ((cp_flags & MM_CP_TRY_CHANGE_WRITABLE) &&
>-			     !pte_write(ptent))
>-				set_write_prot_commit_flush_ptes(vma, folio, page,
>-				addr, pte, oldpte, ptent, nr_ptes, tlb);
>-			else
>-				prot_commit_flush_ptes(vma, addr, pte, oldpte, ptent,
>-					nr_ptes, /* idx = */ 0, /* set_write = */ false, tlb);
>+			if (likely(nr_ptes == 1)) {

Are there any numbers for this optimization? While I am all for optimizing the common
case, it seems unfair to penalize the uncommon one here. Why is nr_ptes > 1 such an
exotic use case (specially today)? ie: How does this change affect the program in
b9bf6c2872c ("mm: refactor MM_CP_PROT_NUMA skipping case into new function"),
which is a series for optimizing large folio cases.

Thanks,
Davidlohr

>+				change_present_ptes(tlb, vma, addr, pte, 1,
>+					end, newprot, folio, page, cp_flags);
>+			} else {
>+				change_present_ptes(tlb, vma, addr, pte,
>+					nr_ptes, end, newprot, folio, page,
>+					cp_flags);
>+			}
>+
> 			pages += nr_ptes;
> 		} else if (pte_none(oldpte)) {
> 			/*
>-- 
>2.53.0
>
>


  parent reply	other threads:[~2026-04-07  0:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-02 14:16 [PATCH v3 0/2] mm/mprotect: micro-optimization work Pedro Falcato
2026-04-02 14:16 ` [PATCH v3 1/2] mm/mprotect: move softleaf code out of the main function Pedro Falcato
2026-04-07  9:58   ` Vlastimil Babka (SUSE)
2026-04-02 14:16 ` [PATCH v3 2/2] mm/mprotect: special-case small folios when applying write permissions Pedro Falcato
2026-04-02 14:21   ` Pedro Falcato
2026-04-02 18:29     ` Andrew Morton
2026-04-06  8:28       ` Pedro Falcato
2026-04-07  0:50   ` Davidlohr Bueso [this message]
2026-04-07  8:21     ` Pedro Falcato
2026-04-07 12:31   ` Vlastimil Babka (SUSE)
2026-04-07 14:01     ` Pedro Falcato
2026-04-02 18:33 ` [PATCH v3 0/2] mm/mprotect: micro-optimization work Andrew Morton
2026-04-06  8:29   ` Pedro Falcato
2026-04-06  9:09     ` David Hildenbrand (arm)
2026-04-06 17:38       ` Andrew Morton
2026-04-07 10:08         ` Lorenzo Stoakes (Oracle)

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=20260407005026.ytf7ed4bk2ljyflx@offworld \
    --to=dave@stgolabs.net \
    --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=pfalcato@suse.de \
    --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