From: Rik van Riel <H.H.vanRiel@phys.uu.nl>
To: Graffiti <ramune@bigfoot.com>
Cc: linux-mm@kvack.org
Subject: Re: [Q] MMU & VM
Date: Fri, 4 Sep 1998 11:53:55 +0200 (MET DST) [thread overview]
Message-ID: <Pine.OSF.3.95.980904115231.12046A-100000@ruunat.phys.uu.nl> (raw)
In-Reply-To: <19980904002057.A5268@ds23-ca-us.dialup>
On Fri, 4 Sep 1998, Graffiti wrote:
> Just how does an MMU work, and why do we need it to implement
> virtual memory instead of handling it all in the kernel?
> I've found quite a few texts on how VM works, but never why we
> need an MMU or what an MMU does.
>
> Can anyone recommend a good book on this?
Well, there's Tanenbaum's "Modern Operating Systems".
There's also a nice VM tutorial from CNE/CMU(?), which
is linked to from the Linux-MM homepage, VM Links.
http://www.phys.uu.nl/~riel/mm-patch/
Rik.
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
next prev parent reply other threads:[~1998-09-04 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-04 7:20 Graffiti
1998-09-04 9:53 ` Rik van Riel [this message]
1998-09-18 20:05 ` estafford
1998-09-18 22:00 ` Zlatko Calusic
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=Pine.OSF.3.95.980904115231.12046A-100000@ruunat.phys.uu.nl \
--to=h.h.vanriel@phys.uu.nl \
--cc=linux-mm@kvack.org \
--cc=ramune@bigfoot.com \
/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