[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090201012553.GB22841@khazad-dum.debian.net>
Date: Sat, 31 Jan 2009 23:25:53 -0200
From: Henrique de Moraes Holschuh <hmh@....eng.br>
To: Pavel Machek <pavel@...e.cz>
Cc: Tim Small <tim@...tersideup.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
ncunningham-lkml@...a.org.au, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, Chris Friesen <cfriesen@...tel.com>,
Doug Thompson <norsk5@...oo.com>,
bluesmoke-devel@...ts.sourceforge.net,
Arjan van de Ven <arjan@...radead.org>
Subject: Re: marching through all physical memory in software
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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists