Date: Sat, 25 Oct 1997 21:42:23 +0000 From: =?iso-8859-1?Q?=DEor=F0ur?= Ivarsson <totii@est.is> To: wghhicks@ix.netcom.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Parity Ram Message-ID: <345267BF.167EB0E7@est.is> References: <Pine.BSF.3.96.971025115335.173A-100000@trojanhorse.ml.org> <34524948.41C67EA6@est.is> <34525F3B.1137B612@ix.netcom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jerry Hicks wrote: > > Žoršur Ivarsson wrote: > > > > This has helped me several times when I was suspecting broken memory in > > the old days (90-93) :-) > > > > Thordur Ivarsson > > ECC Memory was marginally useful for this years ago when were using NMOS > RAM. Lately, most memory failures I've seen are catastrophic, taking out > a whole device or better. > > I'm not a hardware specialist; Does 'Parity RAM' employ a conventional > parity scheme, a la asynch serial communications? > > Didn't Richard Hamming show these to -cause- more problems than they > solve? It seems I recall a number like 256K (bits/bytes/words?) as being > the threshold in a proof he presented. > > Jerry Hicks > jerry_hicks@bigfoot.com In the old days 8088, 8086, 80186, 80286 and 80386 it was just plain odd or even parity like in serial communications but later on came better algorithm that could really fix wrong bits Thordur Ivarsson
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?345267BF.167EB0E7>