Date: Tue, 15 Sep 2015 23:19:31 +0100 From: Igor Mozolevsky <igor@hybrid-lab.co.uk> To: Jim Thompson <jim@netgate.com> Cc: Dieter BSD <dieterbsd@gmail.com>, Hackers freeBSD <freebsd-hackers@freebsd.org>, freebsd-hardware@freebsd.org Subject: Re: ECC support Message-ID: <CADWvR2h4XdYfy3i6zjLqC04uqihNwL9QtTgGN%2BZ8QbAkh9=%2BZA@mail.gmail.com> In-Reply-To: <41EFCF21-D3B0-4EC4-8EAB-417CA33821FC@netgate.com> References: <CAA3ZYrBXZn1WpHWYGJYWJDPsk7iDahCas8RhnHC4w%2Babf4w4hA@mail.gmail.com> <41EFCF21-D3B0-4EC4-8EAB-417CA33821FC@netgate.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 15 September 2015 at 22:52, Jim Thompson <jim@netgate.com> wrote: <snip> Errors are corrected "on-the-fly," corrected data is almost never placed > back in memory. If the same corrupt data is read again, the correction > process is repeated. Replacing the data in memory would require processing > overhead that could accumulate and significantly diminish system > performance. If the error occurred because of random events and isn't a > defect in the memory, the memory address will be cleaned of the error when > the data is overwritten with other data. > <snip> Just to correct a small oversight- most (if not all?) boards have an option to scrub ECC memory in the background so as to prevent single bit (recoverable) errors from turning into double bit (irrecoverable but detectable) errors ;-) -- Igor M.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADWvR2h4XdYfy3i6zjLqC04uqihNwL9QtTgGN%2BZ8QbAkh9=%2BZA>