From: Ralf Baechle <ralf@oss.sgi.com>
To: "Gopakumar.C.E" <gopkumar@cisco.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: Documentation
Date: Fri, 29 Mar 2002 23:42:00 -0800 [thread overview]
Message-ID: <20020329234200.B31160@dea.linux-mips.net> (raw)
In-Reply-To: <0203222102032M.00789@localhost>; from gopkumar@cisco.com on Fri, Mar 22, 2002 at 09:02:03PM +0530
On Fri, Mar 22, 2002 at 09:02:03PM +0530, Gopakumar.C.E wrote:
> Is there any good documentation on how the Linux/Unix code is designed for
> the MIPS processors ? (like how they handle paging, protection etc?)
The whole VM code is largely generic code sprinkled with a few architecture
specific bits all over include/asm-mips and arch/mips. The MIPS specific
bits primarily deal with very low level details of memory managment (TLB,
caches) which the actual paging stuff is in the mm/ directory.
I've not document the MIPS-specific parts of memory managment very well
(standard reason - so much work to do, so little time to do it ...) so
feel free to ask me. The generic Linux memory managment is fairly well
documented in various online resources or a variety of technical books
from your favorite CS bookstore ...
Ralf
prev parent reply other threads:[~2002-03-30 7:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-22 15:32 Documentation Gopakumar.C.E
2002-03-30 7:42 ` Ralf Baechle [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=20020329234200.B31160@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=gopkumar@cisco.com \
--cc=linux-mips@oss.sgi.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