From: Ivan Djelic <ivan.djelic@parrot.com>
To: Gerlando Falauto <gerlando.falauto@keymile.com>
Cc: "Bigler, Stefan" <Stefan.Bigler@keymile.com>,
Christopher Harvey <charvey@matrox.com>,
"Brunck, Holger" <Holger.Brunck@keymile.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: state of support for "external ECC hardware"
Date: Thu, 8 Nov 2012 20:07:14 +0100 [thread overview]
Message-ID: <20121108190714.GD28118@parrot.com> (raw)
In-Reply-To: <509BDE9B.3080909@keymile.com>
On Thu, Nov 08, 2012 at 04:32:27PM +0000, Gerlando Falauto wrote:
(...)
> Right, datasheets and TNs don't even mention what the threshold actually
> is. They just say "Rewrite recommended". Perhaps you could get some
> feeling while running your tests? I mean, if you could get bitflips by
> using host-software ECC (within a reasonable time), and after enabling
> on-die ECC you couldn't anymore, it probably means HW ECC won't tell you
> about bitflips until they reach a number higher than 1. Am I right?
>
> [Did you ever ask Micron by any chance?]
IIRC, Micron on-die ECC reports a "rewrite recommended" status when the
number of bitflips has reached the internal error correction capability
(4 in my case). In other words, a "rewrite recommended" means you should
rewrite the block ASAP before an additional bitflip triggers an ECC failure.
--
Ivan
next prev parent reply other threads:[~2012-11-08 19:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 20:42 state of support for "external ECC hardware" Christopher Harvey
2012-11-08 11:02 ` Gerlando Falauto
2012-11-08 15:21 ` Christopher Harvey
2012-11-08 16:32 ` Gerlando Falauto
2012-11-08 16:37 ` Gerlando Falauto
2012-11-08 17:03 ` Christopher Harvey
2012-11-08 17:02 ` Christopher Harvey
2012-11-08 19:07 ` Ivan Djelic [this message]
2012-11-09 8:46 ` Ricard Wanderlof
2012-11-12 17:19 ` Gerlando Falauto
2012-11-12 17:35 ` Ivan Djelic
2012-11-12 17:39 ` Gerlando Falauto
2012-11-12 18:52 ` Ivan Djelic
2012-11-14 10:12 ` Gerlando Falauto
2012-11-14 13:24 ` Angus CLARK
2012-11-14 14:48 ` Matthieu CASTET
2012-11-14 20:22 ` Ivan Djelic
2012-11-20 11:13 ` Calvin Johnson
2012-11-20 11:35 ` Gerlando Falauto
2012-11-20 12:12 ` Calvin Johnson
2012-11-20 16:16 ` Ricard Wanderlof
2012-11-08 18:59 ` Ivan Djelic
2012-11-08 19:22 ` Christopher Harvey
2012-11-08 19:33 ` Ivan Djelic
2012-11-08 18:04 ` Ivan Djelic
2012-11-14 10:59 ` Angus CLARK
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=20121108190714.GD28118@parrot.com \
--to=ivan.djelic@parrot.com \
--cc=Holger.Brunck@keymile.com \
--cc=Stefan.Bigler@keymile.com \
--cc=charvey@matrox.com \
--cc=gerlando.falauto@keymile.com \
--cc=linux-mtd@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.