From: Matthew Wilcox <willy@infradead.org>
To: Ethan Nelson-Moore <enelsonmoore@gmail.com>
Cc: Lorenzo Stoakes <ljs@kernel.org>,
"Liam R. Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-mm@kvack.org, linux-doc@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH v2] docs/mm: describe current criteria for enabling split page table lock for PTE tables
Date: Mon, 15 Jun 2026 23:36:41 +0100 [thread overview]
Message-ID: <ajB-ebLDYB-pX-4h@casper.infradead.org> (raw)
In-Reply-To: <20260615222829.17420-1-enelsonmoore@gmail.com>
On Mon, Jun 15, 2026 at 03:28:29PM -0700, Ethan Nelson-Moore wrote:
> -Split page table lock for PTE tables is enabled compile-time if
> -CONFIG_SPLIT_PTLOCK_CPUS (usually 4) is less or equal to NR_CPUS.
> +Split page table lock for PTE tables is enabled compile-time (via
is enabled _at_ compile time?
> +CONFIG_SPLIT_PTE_PTLOCKS) if NR_CPUS is greater than or equal to 4 and an
> +MMU is being used. However, it is not supported on some architectures.
> If split lock is disabled, all tables are guarded by mm->page_table_lock.
>
> Split page table lock for PMD tables is enabled, if it's enabled for PTE
> --
> 2.43.0
>
>
next prev parent reply other threads:[~2026-06-15 22:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 22:28 [PATCH v2] docs/mm: describe current criteria for enabling split page table lock for PTE tables Ethan Nelson-Moore
2026-06-15 22:36 ` Matthew Wilcox [this message]
2026-06-15 22:40 ` Ethan Nelson-Moore
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=ajB-ebLDYB-pX-4h@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=david@kernel.org \
--cc=enelsonmoore@gmail.com \
--cc=liam@infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=surenb@google.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