home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.programmer.win32
- Path: sparky!uunet!milo!grebyn!daily!richk
- From: richk@grebyn.com (Richard Krehbiel)
- Subject: Re: Microsoft Systems Journal on NT
- Message-ID: <1992Jul24.010250.1469@grebyn.com>
- Organization: Grebyn Timesharing
- References: <BrpzzM.1HJ@undergrad.math.waterloo.edu> <6830001@hprnd.rose.hp.com> <92Jul23.101729edt.16807@ois.db.toronto.edu>
- Date: Fri, 24 Jul 1992 01:02:50 GMT
- Lines: 18
-
- In article <92Jul23.101729edt.16807@ois.db.toronto.edu> fche@db.toronto.edu writes:
- >There was a quite disgusting detail in the article about memory management -
- >there the VM port to the R4000 chip. It appears that MS has decided to
- >make the very powerful R4000 fit into the mold of the 386 by just about
- >ignoring the R4000's native VM support (which is less complex than that
- >of the 386, but is just as capable) and emulating _in_software_ the
- >multilevel page table system that the 386 uses. Presumably this was done
- >in order to lift a lot more code from the 386 VM code than otherwise,
- >that is, to shorten development overall time.
-
- As I understand it, the R4000 (and R3000 and R2000 and R6000 before
- it) has absolutely *no* hardware page table support. It simply has a
- TLB. Therefore some software for page tables would have been
- necessary anyway. Emulating Intel page tables is one way to take it
- from there, I suppose.
- --
- Richard Krehbiel richk@grebyn.com
- OS/2 2.0 will do for me until AmigaDOS for the 386 comes along...
-