From: Linus Walleij <linus.walleij@linaro.org>
To: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
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>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: Re: [PATCH v5] Documentation/mm: Initial page table documentation
Date: Mon, 19 Jun 2023 10:16:56 +0200 [thread overview]
Message-ID: <CACRpkdaDLuryeFwq0tKzDUoyWagRf_w7BfhOuC8K-o-mhk2g_g@mail.gmail.com> (raw)
In-Reply-To: <3045029.CbtlEUcBR6@suse>
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.
I have understood that some think this, perhaps the intro could use
some dieting, what about sending a patch to make it look like you
want it to?
> The proposed addition appears to be a combination of trivia and a basic
> Operating Systems I course that one might encounter during their second year
> as an undergraduate student studying Computer Science or Computer Engineering.
>
> AFAIK, these concepts are already taught extensively to individuals pursuing a
> B.Sc. degree in Computer Science or a related field, both in Italy, where I
> live, and elsewhere.
Knowing the audience is always the hard part of wording technical
documentation, not the contents per se. I might fail, I might be slight off,
my co-developers are there to help.
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.
Memory management may be different though? Mel having written
his PhD thesis about the Linux VMM and all might set the bar higher
for contributors. I don't know really. But the documentation is not there
just for the MM contributors, as the MM primitives are found sprinkled
all over the kernel.
Yours,
Linus Walleij
next prev parent reply other threads:[~2023-06-19 8:17 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 [this message]
2023-06-21 1:10 ` Fabio M. De Francesco
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=CACRpkdaDLuryeFwq0tKzDUoyWagRf_w7BfhOuC8K-o-mhk2g_g@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=fmdefrancesco@gmail.com \
--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