Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site peora.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!vax135!petsd!peora!jer From: jer@peora.UUCP (J. Eric Roskos) Newsgroups: net.micro Subject: Re: 386 Family Products Message-ID: <1770@peora.UUCP> Date: Mon, 4-Nov-85 08:57:27 EST Article-I.D.: peora.1770 Posted: Mon Nov 4 08:57:27 1985 Date-Received: Tue, 5-Nov-85 09:29:06 EST References: <129@intelca.UUCP> <392@aum.UUCP> <225@l5.uucp> <533@scirtp.UUCP> <2353@ukma.UUCP> Organization: Perkin-Elmer SDC, Orlando, Fl. Lines: 28 > Or how about running a program that requires 64 terabytes of memory? The latest fad in making better microcomputers seems to be in adding some more address bits... now we've got a microcomputer that can run programs "that require 64 terabytes of memory". I'd like to see the memory system for such a computer! It certainly would be big. [Oh, they're "virtual" terabytes, you say! So now we need a 64 terabyte paging device... not to mention questions like "how long would it take just to access 64 terabytes of memory sequentially"... This is not meant to be critical of larger address spaces, just the way they are casually mentioned as a big feature of a small machine.] > By the way, do I note a bit of unwillingness to listen to someone (or > something) just be-cause he (it) is black? I thought they were gold and purple? :-) PS - by the way, if our calculations are right, using 100ns memory (and assuming you just accessed the memory and didn't do anything else, e.g., instruction fetches, etc.), it would take 74.07 days just to read through a 64 terabyte memory one time... -- Shyy-Anzr: J. Eric Roskos UUCP: Ofc: ..!{decvax,ucbvax,ihnp4}!vax135!petsd!peora!jer Home: ..!{decvax,ucbvax,ihnp4}!vax135!petsd!peora!jerpc!jer US Mail: MS 795; Perkin-Elmer SDC; 2486 Sand Lake Road, Orlando, FL 32809-7642