From owner-freebsd-hardware  Wed Dec 18 15:46:43 1996
Return-Path: <owner-hardware>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id PAA10447
          for hardware-outgoing; Wed, 18 Dec 1996 15:46:43 -0800 (PST)
Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA10439
          for <freebsd-hardware@freebsd.org>; Wed, 18 Dec 1996 15:46:41 -0800 (PST)
Received: (from asami@localhost) by vader.cs.berkeley.edu (8.8.4/8.7.3) id PAA03810; Wed, 18 Dec 1996 15:46:27 -0800 (PST)
Date: Wed, 18 Dec 1996 15:46:27 -0800 (PST)
Message-Id: <199612182346.PAA03810@vader.cs.berkeley.edu>
To: richard@pegasus.com
CC: freebsd-hardware@freebsd.org
In-reply-to: <199612181810.IAA03525@pegasus.com> (richard@pegasus.com)
Subject: Re: EDO parit RAM (Was Re: Tyan ...)
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-hardware@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

 * So what kind of impact does this have on `make world'?
 * 
 * It can't be *that* bad -- unless ECC disables the cache ...
 * 
 * I think your benchmark is hitting a sour-spot.

Well, I didn't actually try a "make world" but the system did seem
extremely sluggish with the ECC turned on.  I couldn't stand it so I
turned it off again....

Satoshi (P5-133, BTW)