public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: roland <devzero@web.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Software based ECC ?
Date: Sat, 11 Aug 2007 02:11:15 -0400	[thread overview]
Message-ID: <12507.1186812675@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 10 Aug 2007 23:16:45 +0200." <000a01c7db93$c75b66c0$eeeea8c0@aldipc>

[-- Attachment #1: Type: text/plain, Size: 1252 bytes --]

On Fri, 10 Aug 2007 23:16:45 +0200, roland said:

> http://pdos.csail.mit.edu/papers/softecc:ddopson-meng/softecc_ddopson-meng.pdf
> 
> "SoftECC : A System for Software Memory Integrity Checking"
> 
> Is it possible to implement something like this within the Linux virtual
> memory subsystem ?

Anything that can be simulated with a Turing machine is *possible*.

The question is how many rocket boosters the pig needs for takeoff.

Hint: The thesis talks about why he didn't implement it for Linux.

> If it can be done, wouldn`t this be a great feature ?

Read section 5.2 of that thesis, particularly this quote from 5.2.2:

"For random word writes, this implies that SoftECC will need an order of
magnitude more compute time than the user-mode code"

Basically, on every single memory page that gets dirtied, we have to then
re-checksum the page (blowing away cache lines in the process).  If you want
to get a feel for it, find the kernel code that recognizes that a page is
dirtied, and just add a few lines there:

	int foo = 0, i;
	for (i=0;i++;<1024) { // adjust for non-4K pages
		foo ^= *(page+i);
	}

and see how much your system crawls.

Personally, I'd recommend just shelling out the bucks for hardware ECC if
the reliability matters.


[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

  parent reply	other threads:[~2007-08-11  6:11 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 [this message]
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
     [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=12507.1186812675@turing-police.cc.vt.edu \
    --to=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