home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!zaphod.mps.ohio-state.edu!cs.utexas.edu!sun-barr!west.West.Sun.COM!news2me.EBay.Sun.COM!exodus.Eng.Sun.COM!appserv.Eng.Sun.COM!doug!dwf
- From: dwf@doug.Eng.Sun.COM (Douglas W. Forehand)
- Newsgroups: comp.sys.sun.hardware
- Subject: Re: Memory capacity of 670MP?
- Date: 18 Dec 1992 19:31:00 GMT
- Organization: Sun Microsystems
- Lines: 34
- Distribution: world
- Message-ID: <lj49nkINN3on@appserv.Eng.Sun.COM>
- References: <1992Dec17.135152.16855@shearson.com>
- Reply-To: dwf@doug.Eng.Sun.COM
- NNTP-Posting-Host: doug
-
- In article 16855@shearson.com, mcortes@shearson.com (Mathew Cortes) writes:
- >correction to my previous post.
- >I failed to mention that 16Mb simms can be used.
- >So those figures are not accurate.
- >That will make capacity of expansion pcb up to 1G.
- >cpu 512 Mb
- >
-
-
- Close, but not quite correct.
-
- The max memory the HARDWARE can deal with is 2.5G. It breaks down as follows:
-
- CPU: 32 16Meg SIMMs = 512Meg
-
- EXPANSION
- MEMORY #1: 64 16Meg SIMMs = 1G
-
- EXPANSION
- MEMORY #2: 64 16Meg SIMMs = 1G
- --
- TOTAL = 2.5G
-
- The max memory SUPPORTED by both Solaris 1.1 & >2.1 is 1G on Sun4m architectures
- (SS10, 6x0MP).
- The keyword here is supported. From what I understand (I'm not a kernel guy so don't
- hold me to it) there is nothing architectural in nature in either of the OS's which
- would prevent you from going >1G. The demand for that configuration just does not
- justify the expense of the debug/validation cycle.
-
- If anybody out there has the $$$ to build that configuration, let me know how it
- goes.
-
- -Doug
-