home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mcsun!news.funet.fi!news.cs.tut.fi!mk59200
- From: mk59200@cs.tut.fi (Kolkka Markku Olavi)
- Newsgroups: comp.sys.amiga.hardware
- Subject: Re: Parity
- Date: 18 Nov 1992 16:13:10 GMT
- Organization: Tampere University of Technology
- Lines: 23
- Distribution: world
- Message-ID: <1edq2nINNr40@cs.tut.fi>
- References: <erd.04mw@kumiss.cmhnet.org> <1992Nov13.155530.7183@elroy.jpl.nasa.gov> <1992Nov16.111001.1@ratty.mits.com.au>
- NNTP-Posting-Host: ketturastas.cs.tut.fi
-
- In article <1992Nov16.111001.1@ratty.mits.com.au> lewis@ratty.mits.com.au writes:
- >>>EDC (Error Detection and Correction) is also known as ECC (why, I don't
- >>>know). On Unibus VAXen, ECC memory is 10 bits/byte; it can *correct*
- >>>single bit errors and detect double bit errors.
- >
- >"The ECC scheme used in the memory subsystem is capable of detecting a single
- >or double bit error. It is also capable of correcting all single bit errors.
- >This is accomplished by storing eight check bits, along with the 64 data bits
- >in each memory location (i.e. quadword access to memory).
-
- So, the ECC system _doesn't_ use 10 (or 9) bits per byte, it uses 72 bits per
- quadword. There is a big difference, even if the total amount of bits is
- similar. With this ECC scheme you cant read or write individual bytes,
- because changing a single byte will affect several checkbits and the new
- values of the checkbits depend on other data in the block.
-
- Of course all this is hidden from the CPU and software by the memory
- controller, but it complicates and slows down the memory/CPU interface.
-
- --
- Markku Kolkka
- mk59200@cc.tut.fi
-
-