From: Bruce Allen <ballen@gravity.phys.uwm.edu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
"linux-os (Dick Johnson)" <linux-os@analogic.com>,
Robert Hancock <hancockr@shaw.ca>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Bruce Allen <bruce.allen@aei.mpg.de>
Subject: Re: ECC and DMA to/from disk controllers
Date: Wed, 12 Sep 2007 22:37:56 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.63.0709122215100.16468@trinity.phys.uwm.edu> (raw)
In-Reply-To: <46E5EAB9.9020504@shaw.ca>
Alan, Robert, Dick,
Thank you all for the informed and helpful response!
Alan, I'll pass your comments on to Peter Kelemen. Not sure if he follows
LKML. I think he'll be interested in your characterization of the error
types. I'll point him to the thread. (I think Peter and his
collaborators are fairly aware of the undetected error rates in standard
ethernet TCP/IP traffic which as I recall is about one undetected
single-bit error per 4TB transfered. I am pretty sure they have ruled
this out since they have checksums computed after any network transfers.)
Robert, Dick, if I have understood correctly, in response to my specific
question, RAID controllers on PCI cards will DMA data into memory over a
PCI bus using one parity bit per 32 data bits for protection. This does
provide some protection against errors in the data transfer, but much less
protection than typical RAM ECC which has one ECC byte for each eight data
bytes. As I recall, many older motherboards disabled parity on the PCI
bus, so even this protection may be inactive in many cases. From a few
minutes of on-line research, I have the impression that PCI-e has better
ECC protection against address/data errors than PCI but I am not certain.
Thanks again!
Cheers,
Bruce
next prev parent reply other threads:[~2007-09-13 3:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.qDlrttL6xIyU0yqEbWvsJiyy5tU@ifi.uio.no>
2007-09-11 1:09 ` Robert Hancock
2007-09-13 3:37 ` Bruce Allen [this message]
2007-09-10 12:19 Bruce Allen
2007-09-10 13:54 ` Alan Cox
2007-09-14 9:32 ` KELEMEN Peter
2007-09-10 18:05 ` linux-os (Dick Johnson)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.63.0709122215100.16468@trinity.phys.uwm.edu \
--to=ballen@gravity.phys.uwm.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bruce.allen@aei.mpg.de \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®