From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>, <linux-mm@kvack.org>,
<linux-doc@vger.kernel.org>,
"Matthew Wilcox" <willy@infradead.org>,
Randy Dunlap <rdunlap@infradead.org>,
"Mike Rapoport" <rppt@kernel.org>
Subject: Re: [PATCH v3] Documentation/mm: Initial page table documentation
Date: Fri, 9 Jun 2023 17:37:23 +0100 [thread overview]
Message-ID: <20230609173723.0000520a@Huawei.com> (raw)
In-Reply-To: <20230608125501.3960093-1-linus.walleij@linaro.org>
On Thu, 8 Jun 2023 14:55:01 +0200
Linus Walleij <linus.walleij@linaro.org> wrote:
> This is based on an earlier blog post at people.kernel.org,
> it describes the concepts about page tables that were hardest
> for me to grasp when dealing with them for the first time,
> such as the prevalent three-letter acronyms pfn, pgd, p4d,
> pud, pmd and pte.
>
> I don't know if this is what people want, but it's what I would
> have wanted.
>
> I discussed at one point with Mike Rapoport to bring this into
> the kernel documentation, so here is a small proposal.
>
> Cc: Matthew Wilcox <willy@infradead.org>
> Cc: Randy Dunlap <rdunlap@infradead.org>
> Cc: Mike Rapoport <rppt@kernel.org>
> Link: https://people.kernel.org/linusw/arm32-page-tables
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Hi Linus,
Reads nicely and seems like a good introduction to me.
One very trivial comment but otherwise FWIW
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> +
> +Over time a deeper hierarchy has been developed in response to increasing memory
> +sizes. When Linux was created, 4KB pages and a single page table called
> +`swapper_pg_dir` with 1024 entries was used, covering 4MB which coincided with
> +the fact that Torvald's first computer had 4MB of physical memory. Entries in
> +this single table was referred to as *PTE*:s - page table entries.
table were referred to as
(entries is plural hence were rather than was)
> +
> +The hierarchy reflects the fact that page table hardware has become hierarchical
next prev parent reply other threads:[~2023-06-09 16:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 12:55 Linus Walleij
2023-06-09 16:37 ` Jonathan Cameron [this message]
2023-06-11 5:24 ` Mike Rapoport
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=20230609173723.0000520a@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rdunlap@infradead.org \
--cc=rppt@kernel.org \
--cc=willy@infradead.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