From: Folkert van Heusden <folkert@vanheusden.com>
To: Valdis.Kletnieks@vt.edu
Cc: roland <devzero@web.de>, linux-kernel@vger.kernel.org
Subject: Re: Software based ECC ?
Date: Sun, 12 Aug 2007 18:51:31 +0200 [thread overview]
Message-ID: <20070812165131.GG7973@vanheusden.com> (raw)
In-Reply-To: <12507.1186812675@turing-police.cc.vt.edu>
> > 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?
Idea: what about a multicore system (3 or more) that runs the same
processes on 2 cores and a third core verifying that they both do the
same? As I think it is not only ram that can become faulty.
Folkert van Heusden
--
MultiTail er et flexible tool for å kontrolere Logfiles og commandoer.
Med filtrer, farger, sammenføringer, forskeliger ansikter etc.
http://www.vanheusden.com/multitail/
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com
next prev parent reply other threads:[~2007-08-12 16:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 21:16 Software based ECC ? roland
2007-08-10 22:21 ` Alan Cox
2007-08-11 6:11 ` Valdis.Kletnieks
2007-08-12 16:51 ` Folkert van Heusden [this message]
2007-08-12 17:07 ` Jan Engelhardt
2007-08-12 19:05 ` chibiryuu
2007-08-13 3:09 ` Valdis.Kletnieks
[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
2007-08-21 20:17 ` 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=20070812165131.GG7973@vanheusden.com \
--to=folkert@vanheusden.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=devzero@web.de \
--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