From owner-freebsd-hackers  Sat Oct 25 13:31:02 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id NAA20844
          for hackers-outgoing; Sat, 25 Oct 1997 13:31:02 -0700 (PDT)
          (envelope-from owner-freebsd-hackers)
Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA20838
          for <freebsd-hackers@FreeBSD.ORG>; Sat, 25 Oct 1997 13:30:59 -0700 (PDT)
          (envelope-from jfieber@indiana.edu)
Received: from localhost (jfieber@localhost)
	by fallout.campusview.indiana.edu (8.8.7/8.8.7) with SMTP id PAA18625;
	Sat, 25 Oct 1997 15:30:57 -0500 (EST)
Date: Sat, 25 Oct 1997 15:30:57 -0500 (EST)
From: John Fieber <jfieber@indiana.edu>
To: "Jamil J. Weatherbee" <jamil@trojanhorse.ml.org>
cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: Parity Ram
In-Reply-To: <Pine.BSF.3.96.971025115335.173A-100000@trojanhorse.ml.org>
Message-ID: <Pine.BSF.3.96.971025152749.18619A-100000@fallout.campusview.indiana.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Sat, 25 Oct 1997, Jamil J. Weatherbee wrote:

> Can someone fill me in on when you would want to use parity ram as opposed
> to non-parity ram these days?

So when your memory fails, you know it was a memory failure
rather than an irreproducable software bug.  Also, with
appropriate BIOS support, you can get not only error detection,
but some error correction capability.

My question is why would anybody want to use non-parity ram?

-john