Article View: net.arch
Article #2711Re: VERY LARGE main memories
From: Thomas J Keller
Date: Tue, 26 Aug 1986 21:06
Date: Tue, 26 Aug 1986 21:06
15 lines
1119 bytes
1119 bytes
Someone please correct me if I am wrong, but as I have been lead to
understand the situation, it will prove somewhat difficult to successfully
implement large physical memory systems on the order of 1Gb. The primary
impediment seems to be the delays caused by propagation delays in the
decoding trees. Anyone care to enlight me (us)?
--
Disclaimer: Disclaimer? DISCLAIMER!? I don't need no stinking DISCLAIMER!!!
tom keller "She's alive, ALIVE!"
{ihnp4, dual}!ptsfa!gilbbs!mc68020
(* we may not be big, but we're small! *)
Technical Details
Message-ID:
<884@gilbbs.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!mnetor!seismo!lll-crg!lll-lcc!well!ptsfa!gilbbs!mc68020References:
<2017@sdcsvax.UUCP>Show Full Headers
Complete Article Headers
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: arc1-ca.pugleaf.net!utzoo!mnetor!seismo!lll-crg!lll-lcc!well!ptsfa!gilbbs!mc68020 From: mc68020@gilbbs.UUCP (Thomas J Keller) Newsgroups: net.arch Subject: Re: VERY LARGE main memories Message-ID: <884@gilbbs.UUCP> Date: Tue, 26-Aug-86 17:06:57 EDT Article-I.D.: gilbbs.884 Posted: Tue Aug 26 17:06:57 1986 Date-Received: Wed, 27-Aug-86 20:57:09 EDT References: <2017@sdcsvax.UUCP> Organization: Gil's Place, Santa Rosa CA Lines: 15 Keywords: memory size Summary: decoding delays seen as major impediment