linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Pavel Machek <pavel@suse.cz>
Cc: Tim Small <tim@buttersideup.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	ncunningham-lkml@crca.org.au, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, Chris Friesen <cfriesen@nortel.com>,
	Doug Thompson <norsk5@yahoo.com>,
	bluesmoke-devel@lists.sourceforge.net,
	Arjan van de Ven <arjan@infradead.org>
Subject: Re: marching through all physical memory in software
Date: Sat, 31 Jan 2009 23:25:53 -0200	[thread overview]
Message-ID: <20090201012553.GB22841@khazad-dum.debian.net> (raw)
In-Reply-To: <20090131212754.GA15243@elf.ucw.cz>

On Sat, 31 Jan 2009, Pavel Machek wrote:
> > You can also implement software-based ECC using a background scrubber
> > and setting aside pages to store the ECC information.  Now, THAT is
> > probably not worth bothering with due to the performance impact, but
> > who knows...
> 
> Actually, that would be quite cool. a) I suspect memory in  my zaurus
> bitrots and b) bitroting memory over s2ram is apprently quite common.

Well, software-based ECC for s2ram (calculate right before s2ram,
check-and-fix right after waking up) is certainly doable and a LOT
easier than my crazy idea of sofware-based generic ECC (which requires
some sort of trick to detect pages that were written to, so that you
can update their ECC information)...

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2009-02-01  1:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <715599.77204.qm@web50111.mail.re2.yahoo.com>
2009-01-30 19:32 ` Eric W. Biederman
2009-01-30 20:20   ` Tim Small
2009-01-31  3:54     ` Eric W. Biederman
2009-01-31 12:48       ` Tim Small
2009-01-31 13:43         ` Henrique de Moraes Holschuh
2009-01-31 21:27           ` Pavel Machek
2009-02-01  1:25             ` Henrique de Moraes Holschuh [this message]
2009-01-30 21:10   ` Nigel Cunningham
2009-02-02 18:29   ` Chris Friesen
2009-02-02 22:45     ` Valdis.Kletnieks
2009-02-03 14:31       ` Chris Friesen
2009-02-03 22:25         ` Pavel Machek
2009-02-04 16:03           ` Chris Friesen
2009-02-04 16:47           ` Dave Jiang
     [not found] <497DD8E5.1040305@nortel.com>
     [not found] ` <20090126075957.69b64a2e@infradead.org>
     [not found]   ` <497F5289.404@nortel.com>
2009-01-27 20:16     ` Eric W. Biederman
2009-01-28 19:38       ` Pavel Machek
2009-01-30  9:05         ` Nigel Cunningham
2009-01-30  9:13           ` Pavel Machek
2009-01-30 13:00             ` Nigel Cunningham

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=20090201012553.GB22841@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --cc=arjan@infradead.org \
    --cc=bluesmoke-devel@lists.sourceforge.net \
    --cc=cfriesen@nortel.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ncunningham-lkml@crca.org.au \
    --cc=norsk5@yahoo.com \
    --cc=pavel@suse.cz \
    --cc=tim@buttersideup.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