From owner-freebsd-hackers Wed Jul 9 15:35:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA16698 for hackers-outgoing; Wed, 9 Jul 1997 15:35:22 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA16691 for ; Wed, 9 Jul 1997 15:35:14 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.5/8.8.5) id RAA01099; Wed, 9 Jul 1997 17:34:31 -0500 (EST) From: "John S. Dyson" Message-Id: <199707092234.RAA01099@dyson.iquest.net> Subject: Re: PQ_LARGECACHE and page colouring In-Reply-To: <199707092048.XAA24685@shadows.aeon.net> from mika ruohotie at "Jul 9, 97 11:48:40 pm" To: bsdhack@shadows.aeon.net (mika ruohotie) Date: Wed, 9 Jul 1997 17:34:31 -0500 (EST) Cc: hackers@FreeBSD.ORG Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > > if I add options PQ_LARGECACHE to the kernel config file. > > > something we with 512K cache should use or not? > > If you have a 512K direct mapped cache, it is significantly > > direct mapped? uh, mine's pipeline burst, fx chipset, soon tx. > (and 64 megs ram, i know not to use more) > The FX chipset definitely supported directed mapped caching, it is likely/possible that TX does also. You'll probably see a perf increase under most circumstances. Actually, it manifests itself as userland CPU operations simply being a little quicker when running large programs. John