From: Bodo Eggert <7eggert@gmx.de>
To: Folkert van Heusden <folkert@vanheusden.com>,
Valdis.Kletnieks@vt.edu, roland <devzero@web.de>,
linux-kernel@vger.kernel.org
Subject: Re: Software based ECC ?
Date: Tue, 21 Aug 2007 20:44:01 +0200 [thread overview]
Message-ID: <E1INYht-0000Xw-Ay@be1.lrz> (raw)
In-Reply-To: 8RoXy-3NJ-13@gated-at.bofh.it
Folkert van Heusden <folkert@vanheusden.com> wrote:
>> > http://pdos.csail.mit.edu/papers/softecc:ddopson-meng
softecc_ddopson-meng.pdf
>> > "SoftECC : A System for Software Memory Integrity Checking"
>>
>> Personally, I'd recommend just shelling out the bucks for hardware ECC if
>> the reliability matters.
>
> a question and an idea: Q: is ecc guaranteed to detect all bitflips?
It's guaranteed not to.
Having n extra bits, you can detect n-bit-flips and correct n/2-bit-flips
(provided you use an optimal code).
These extra bits can flip, too, so if you have m >= 1 data bits and any
finite number n of extra bits, it's possible to have an undetectable
n+1-bit-flip.
--
If you can't remember, then the claymore IS pointed at you.
Friß, Spammer: W@2fzbe.7eggert.dyndns.org k@-.7eggert.dyndns.org
Rtc@Ytzq.7eggert.dyndns.org 9qKSiPo@ZesTis.7eggert.dyndns.org
next parent reply other threads:[~2007-08-21 18:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8QK3R-kc-9@gated-at.bofh.it>
[not found] ` <8QSuw-4J2-9@gated-at.bofh.it>
[not found] ` <8RoXy-3NJ-13@gated-at.bofh.it>
2007-08-21 18:44 ` Bodo Eggert [this message]
2007-08-21 20:17 ` Software based ECC ? linux-os (Dick Johnson)
2007-08-10 21:16 roland
2007-08-10 22:21 ` Alan Cox
2007-08-11 6:11 ` Valdis.Kletnieks
2007-08-12 16:51 ` Folkert van Heusden
2007-08-12 17:07 ` Jan Engelhardt
2007-08-12 19:05 ` chibiryuu
2007-08-13 3:09 ` Valdis.Kletnieks
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=E1INYht-0000Xw-Ay@be1.lrz \
--to=7eggert@gmx.de \
--cc=Valdis.Kletnieks@vt.edu \
--cc=devzero@web.de \
--cc=folkert@vanheusden.com \
--cc=linux-kernel@vger.kernel.org \
/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