From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: "Liam R . Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>, Jann Horn <jannh@google.com>,
Alice Ryhl <aliceryhl@google.com>,
Boqun Feng <boqun.feng@gmail.com>,
Matthew Wilcox <willy@infradead.org>,
Mike Rapoport <rppt@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, Suren Baghdasaryan <surenb@google.com>,
Hillf Danton <hdanton@sina.com>,
Qi Zheng <zhengqi.arch@bytedance.com>,
SeongJae Park <sj@kernel.org>
Subject: Re: [PATCH] docs/mm: add VMA locks documentation
Date: Fri, 8 Nov 2024 19:25:38 +0700 [thread overview]
Message-ID: <Zy4DQmWHpC_QMGTP@archie.me> (raw)
In-Reply-To: <20241107190137.58000-1-lorenzo.stoakes@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 447 bytes --]
On Thu, Nov 07, 2024 at 07:01:37PM +0000, Lorenzo Stoakes wrote:
> +.. note:: In instances where the architecture supports fewer page tables than
> + five the kernel cleverly 'folds' page table levels, that is skips them within
> + the logic, regardless we can act as if there were always five.
What are being skipped if e.g. we only have 3 or 4 page tables?
Confused...
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-11-08 12:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 19:01 Lorenzo Stoakes
2024-11-07 21:15 ` Jann Horn
2024-11-08 10:35 ` Lorenzo Stoakes
2024-11-08 8:26 ` Kirill A. Shutemov
2024-11-08 8:59 ` Lorenzo Stoakes
2024-11-08 12:25 ` Bagas Sanjaya [this message]
2024-11-08 12:29 ` Lorenzo Stoakes
2024-11-08 12:34 ` Lorenzo Stoakes
2024-11-12 1:12 ` Bagas Sanjaya
2024-11-11 2:42 ` Wei Yang
2024-11-11 10:31 ` Lorenzo Stoakes
2024-11-11 7:07 ` Wei Yang
2024-11-11 10:39 ` Lorenzo Stoakes
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=Zy4DQmWHpC_QMGTP@archie.me \
--to=bagasdotme@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=aliceryhl@google.com \
--cc=boqun.feng@gmail.com \
--cc=corbet@lwn.net \
--cc=hdanton@sina.com \
--cc=jannh@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=rppt@kernel.org \
--cc=sj@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--cc=zhengqi.arch@bytedance.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