From owner-freebsd-hackers Mon May 13 11:30:39 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA11444 for hackers-outgoing; Mon, 13 May 1996 11:30:39 -0700 (PDT) Received: from nol.net (root@dazed.nol.net [206.126.32.101]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA11420 Mon, 13 May 1996 11:30:27 -0700 (PDT) Received: from dazed.nol.net (blh@dazed.nol.net [206.126.32.101]) by nol.net (8.7.5/8.7.3) with SMTP id NAA12806; Mon, 13 May 1996 13:24:53 -0500 (CDT) X-AUTH: NOLNET SENDMAIL AUTH Date: Mon, 13 May 1996 13:24:52 -0500 (CDT) From: "Brett L. Hawn" To: "matthew c. mead" cc: Joe Greco , hackers@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: Triton chipset with 256k cache caches 32M only? In-Reply-To: <199605131336.JAA23402@neon.Glock.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 13 May 1996, matthew c. mead wrote: > Joe Greco writes: > > > > I've got two machine with moderately fast CPUs in them. One > > > is a Cyrix 6x86 120+ (@100Mhz), and the other is a P90 (clocked > > > to 100Mhz). When I have 40M in the machines, the upper 8M is not > > > cached, and my performance is roughly 2/3 of that when they just > > > have 32M and all of the memory is cached. > > > > Does anyone know for sure whether or not 256K cache Triton > > > chipsets only cache up to 32M? Anyone know what I can do to get > > > the other 8M cached as well? I'd really like to have that extra > > > 8M in there, but at 2/3 the performance, it aint gonna happen. > > > Any help is greatly appreciated! > > > My impression was 64M, based on past discussions with Rod Grimes. > > Hmm. That would then imply that there's something wrong > with each of these boards, or that the manufacturer is lazy. > Does anyone know if going to 512K cache will allow me to cache on > all 40M ram? Thanks! Assuming that these are Triton-1 chipsets you will find that anything over 64m leads to non-caching. I would highly suggest getting some of the new ASUS (just my particular favorite) tr-2 chipset motherboards, these solve the caching problem along with many of the other inherent bugs of tr-1 chipsets. Brett