Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!ukc!axion!cam-cl!cet1 From: cet1@cl.cam.ac.uk (C.E. Thompson) Newsgroups: comp.arch Subject: Re: 64-bit addresses Message-ID: <1786@gannet.cl.cam.ac.uk> Date: 1 Mar 90 17:36:35 GMT References: Sender: news@cl.cam.ac.uk Reply-To: cet1@cl.cam.ac.uk (C.E. Thompson) Organization: U of Cambridge Comp Lab, UK Lines: 21 In article wayne@dsndata.uucp (Wayne Schlitt) asks: >what is the difference between "main" memory and "expanded" memory? >if "expanded" memory is just a back store for paging and disk cache, >then i dont think that including "expanded" memory is what people >normally think of as "physical memory". (you can also exclude ram >disks and the memory on high res video cards) > On IBM 3090s (probably the mainframe that the previous poster had in mind) "expanded storage" is RAM which is not directly addressable, but is moved in 4Kbyte chunks to and from directly addressable storage by synchronous instructions. It is used by MVS and VM as a very-high-speed paging device; microcode assists can do the transfers without a software page fault in some circumstances. If someone would like to explain what the economic advantages are to providing extra storage in this form, I would be interested to listen. Chris Thompson JANET: cet1@uk.ac.cam.phx Internet: cet1%phx.cam.ac.uk@nsfnet-relay.ac.uk