From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: linux-mm@kvack.org, linux-doc@vger.kernel.org,
Matthew Wilcox <willy@infradead.org>,
Randy Dunlap <rdunlap@infradead.org>,
Mike Rapoport <rppt@kernel.org>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: Re: [PATCH v5] Documentation/mm: Initial page table documentation
Date: Wed, 21 Jun 2023 03:10:19 +0200 [thread overview]
Message-ID: <13291493.dW097sEU6C@suse> (raw)
In-Reply-To: <CACRpkdaDLuryeFwq0tKzDUoyWagRf_w7BfhOuC8K-o-mhk2g_g@mail.gmail.com>
On lunedì 19 giugno 2023 10:16:56 CEST Linus Walleij wrote:
> On Sun, Jun 18, 2023 at 3:16 PM Fabio M. De Francesco
>
> <fmdefrancesco@gmail.com> wrote:
> > I am writing to express my dissent regarding the proposal to add basic
> > information about the role of hierarchical (multi-level) page tables in
> > mapping virtual memory to physical page frames.
[...]
> Assuming that newcomers to the Linux kernel have formal academic
> background or specifically operating system education is a bit thick
> IMO, suffice to read pages 108-111 of Glyn Moody's book
> "Rebel Code" about the background of the network maintainer.
> There are a whole bunch of random people attracted to Linux
> development.
Linus,
I must admit that I have had a change of heart regarding the necessity of this
documentation.
This change came about after reading Jon's reply, as well as your own.
However, it wasn't just because of the two of you. It was mainly due to my
conversations with some colleagues I work with, who hold M.Sc. degrees in
Computer Science.
Despite not having a formal background in CS or CE myself, I have taken the
time to self-teach the subject matter, which I expected them to be well-versed
in.
To my surprise, they only have a vague understanding of page tables and the
fact that processes use addresses that may not correspond to physical
locations. That's about it!
Hence, I now fully support your initiative and want to express my gratitude
for undertaking this task.
The only thing I would prefer not to see is the historical reference to the
first implementation of hierarchical page tables. After all, many concepts
implemented in Linux are derived or adapted from existing knowledge or
implementations in other kernels. However, I can also understand why you
prefer to have it as an introduction to the subject.
Once again thanks,
Fabio
next prev parent reply other threads:[~2023-06-21 1:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 7:25 Linus Walleij
2023-06-16 14:14 ` Jonathan Corbet
2023-06-18 13:16 ` Fabio M. De Francesco
2023-06-18 18:54 ` Jonathan Corbet
2023-06-19 8:16 ` Linus Walleij
2023-06-21 1:10 ` Fabio M. De Francesco [this message]
2023-06-21 7:35 ` Linus Walleij
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=13291493.dW097sEU6C@suse \
--to=fmdefrancesco@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=bagasdotme@gmail.com \
--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