Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!caip!clyde!burl!ulysses!bellcore!whuxcc!lcuxlm!whuxl!houxm!hropus!jin From: jin@hropus.UUCP (Jerry Natowitz) Newsgroups: net.arch Subject: Re: Paging Message-ID: <654@hropus.UUCP> Date: Thu, 4-Sep-86 09:00:39 EDT Article-I.D.: hropus.654 Posted: Thu Sep 4 09:00:39 1986 Date-Received: Fri, 5-Sep-86 03:21:52 EDT References: <8494@duke.duke.UUCP> <147@eneevax.UUCP> <536@cubsvax.UUCP> Distribution: na Organization: Bell Labs, Holmdel, NJ Lines: 23 > If big main memory gets REALLY cheap, maybe we won't need virtual memory any > more. Most jobs could just grab a partition of core and live there till they > die. Another partition could be used to run a virtual machine in for bigger > jobs, which perhaps could be run as batch jobs in off-hours more profitably... > > Peter S. Shenkin Columbia Univ. Biology Dept., NY, NY 10027 > {philabs,rna}!cubsvax!peters cubsvax!peters@columbia.ARPA I think my definition of virtual memory might be out of synch with others. Cheap large memories mean that we would be able to do away with demand paging. We would still need address translation unless every process was written in position independent code (no address constants at assembly/compile time etc.) Does virtual memory imply demand paging or just address translation? -- Jerry Natowitz (HASA - A division) Bell Labs HR 2A-214 201-615-5178 (no CORNET) ihnp4!houxm!hropus!jin or ihnp4!opus!jin Isn't it interesting how the beautiful little red flower in the forest becomes so ugly when you discover it's a candy wrapper.