From owner-freebsd-hackers Sun Oct 26 23:24:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA22038 for hackers-outgoing; Sun, 26 Oct 1997 23:24:24 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA22033 for ; Sun, 26 Oct 1997 23:24:19 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 2724 invoked by uid 1001); 27 Oct 1997 07:24:14 +0000 (GMT) To: jamil@trojanhorse.ml.org Cc: hackers@FreeBSD.ORG Subject: Re: Parity Ram In-Reply-To: Your message of "Sun, 26 Oct 1997 22:37:47 -0800 (PST)" References: X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 27 Oct 1997 08:24:14 +0100 Message-ID: <2722.877937054@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > How about ECC in ram, like object checksums on the HP 48. What is it you want to do? ECC based on parity memory is fairly inexpensive. You need 12.5% more bits, total, and a chipset that can handle ECC. This lets you correct all single bit errors and detect all double bit errors (also many multiple bit errors). What more do you want? Steinar Haug, Nethelp consulting, sthaug@nethelp.no