Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!uw-beaver!tektronix!zeus!bobr
From: bobr@zeus.TEK.COM (Robert Reed)
Newsgroups: comp.sys.ibm.pc,comp.arch,comp.unix.wizards
Subject: Re: 386 demand paged virtual memory
Message-ID: <2349@zeus.TEK.COM>
Date: Thu, 3-Sep-87 19:33:00 EDT
Article-I.D.: zeus.2349
Posted: Thu Sep  3 19:33:00 1987
Date-Received: Sat, 5-Sep-87 16:38:40 EDT
References: <125@snark.UUCP> <299@nuchat.UUCP> <358@netxcom.UUCP> <268@etn-rad.UUCP>
Reply-To: bobr@zeus.UUCP (Robert Reed)
Organization: CAE Systems Division, Tektronix Inc., Beaverton OR
Lines: 16
Xref: mnetor comp.sys.ibm.pc:7462 comp.arch:2076 comp.unix.wizards:4074

In article <268@etn-rad.UUCP> jru@etn-rad.UUCP (0000-John Unekis) writes:
	In article <358@netxcom.UUCP> jallen@netxcom.UUCP (John Allen) writes:

	What else would one need?

    When they say that the 80386 "supports demand paged virtual memory",
    what they mean is that since your operating system will have to manage
    tasks as a group of segments in memory anyway, why not make the segments
    a small fixed size and call them pages instead.

However, the 386 has both segment tables and page tables, which, in addition
to the previously mentioned features, does provide for real demand paged
virtual memory.  You can run with a segmented architecture or a
paged-segmented architecture, or just a paged architecture, all using a 386.
-- 
Robert Reed, Tektronix CAE Systems Division, bobr@zeus.TEK