* Documentation
@ 2002-03-22 15:32 Gopakumar.C.E
2002-03-30 7:42 ` Documentation Ralf Baechle
0 siblings, 1 reply; 2+ messages in thread
From: Gopakumar.C.E @ 2002-03-22 15:32 UTC (permalink / raw)
To: linux-mips
Hi,
Is there any good documentation on how the Linux/Unix code is designed for
the MIPS processors ? (like how they handle paging, protection etc?)
Thanks
Gopakumar.C.E
--
"Vidhya dadathi vinayam" - Education leads to humility (in sanskrit).
--------------------------------
http://www.geocities.com/gopakumar_ce/
http://wwwin-people.cisco.com/gopkumar/
--------------------------------
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Documentation
2002-03-22 15:32 Documentation Gopakumar.C.E
@ 2002-03-30 7:42 ` Ralf Baechle
0 siblings, 0 replies; 2+ messages in thread
From: Ralf Baechle @ 2002-03-30 7:42 UTC (permalink / raw)
To: Gopakumar.C.E; +Cc: linux-mips
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-03-30 7:42 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-03-22 15:32 Documentation Gopakumar.C.E
2002-03-30 7:42 ` Documentation Ralf Baechle
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox