From: cartercheng@gmail.com (Carter Cheng)
To: kernelnewbies@lists.kernelnewbies.org
Subject: MMU related code
Date: Mon, 29 Oct 2018 16:01:02 +0800 [thread overview]
Message-ID: <CALS6=qURqc2i5MPZS8rrGAMRk0M=YHYHcfu4a8oovAX3+VkKvg@mail.gmail.com> (raw)
In-Reply-To: <20181029074515.tmxhq22wx3lmedyc@cam.home.0l.dn42>
Thanks, I'll check it out.
On Mon, Oct 29, 2018 at 3:45 PM Steffen Vogel <post@steffenvogel.de> wrote:
> Hi Carter,
>
> On Mon, Oct 29, 2018 at 03:33:02PM +0800, Carter Cheng wrote:
> > Is the /mm directory the correct place to look? It seems to contain
> memory
> > related code but from what little I have read it seems at a higher level
> > building in some cases at least on kmalloc.
>
> Most if the paging/MMU code is also architecture specific which means
> that it resides in the arch/mm subfolders.
>
> I saw that there was a MM 101 presentation last week at the Open Source
> Summit [1], Unfortunatetly, it is quite high-level and most likelt
> uninterestting to you.
>
> But there is also a huge subsection in the official kernel documentation
> which has many references to the mm/ and arch/mm code [2].
>
> Cheers,
> Steffen
>
>
> [1]
> https://events.linuxfoundation.org/wp-content/uploads/2017/12/MM-101-Introduction-to-Linux-Memory-Management-Christoph-Lameter-Jump-Trading-LLC.pdf
> [2] https://www.kernel.org/doc/html/latest/vm/index.html
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20181029/e4417a0a/attachment.html>
prev parent reply other threads:[~2018-10-29 8:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-28 16:08 MMU related code Carter Cheng
2018-10-29 1:49 ` valdis.kletnieks at vt.edu
2018-10-29 2:44 ` SeyedAlireza Sanaee
2018-10-29 7:33 ` Carter Cheng
2018-10-29 7:45 ` Steffen Vogel
2018-10-29 8:01 ` Carter Cheng [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='CALS6=qURqc2i5MPZS8rrGAMRk0M=YHYHcfu4a8oovAX3+VkKvg@mail.gmail.com' \
--to=cartercheng@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).