From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Ira Weiny <ira.weiny@intel.com>,
Matthew Wilcox <willy@infradead.org>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH] Documentation/page_tables: Add info about MMU/TLB and Page Faults
Date: Wed, 09 Aug 2023 15:00:31 +0200 [thread overview]
Message-ID: <3770829.kQq0lBPeGt@suse> (raw)
In-Reply-To: <20230807105010.GK2607694@kernel.org>
On lunedì 7 agosto 2023 12:50:10 CEST Mike Rapoport wrote:
> Hi Fabio,
>
> On Fri, Jul 28, 2023 at 01:53:01PM +0200, Fabio M. De Francesco wrote:
> > Extend page_tables.rst by adding a section about the role of MMU and TLB
> > in translating between virtual addresses and physical page frames.
> > Furthermore explain the concept behind Page Faults and how the Linux
> > kernel handles TLB misses. Finally briefly explain how and why to disable
> > the page faults handler.
> >
> > [snip]
> >
> > +MMU, TLB, and Page Faults
> > +=========================
> > +
> > +The `Memory Management Unit (MMU)` is a hardware component that handles
> > virtual +to physical address translations. It may use relatively small
> > caches in hardware +called `Translation Lookaside Buffers (TLBs)` and
`Page
> > Walk Caches` to speed up +these translations.
> > +
> > +When a process wants to access a memory location, the CPU provides a
> > virtual
> > +address to the MMU, which then uses the MMU to check access permissions
and
> > +dirty bits, and if possible it resolves the physical address and consents
> > the +requested type of access to the corresponding physical address.
>
> Essentially any access to a memory location involves the translation from
> virtual to physical, not only when processes access memory.
Mike,
I'm cutting everything from here on because I agree with your comments, so I
could just write a long list of 'I agree', 'I understand' and the like. I want
to avoid readers from the aforementioned list :-)
I think (actually, I hope) that I have understood everything correctly. I will
send a new version with the necessary corrections by the end of this week.
Thanks again for your comments and suggestions.
Fabio
prev parent reply other threads:[~2023-08-09 13:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 11:53 Fabio M. De Francesco
2023-08-03 17:08 ` Fabio M. De Francesco
2023-08-07 9:40 ` Linus Walleij
2023-08-09 13:27 ` Fabio M. De Francesco
2023-08-07 10:50 ` Mike Rapoport
2023-08-09 13:00 ` Fabio M. De Francesco [this message]
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=3770829.kQq0lBPeGt@suse \
--to=fmdefrancesco@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=ira.weiny@intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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