From: Artem Bityutskiy <dedekind1@gmail.com>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: "Steffen Kühn" <sk@ammonit.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: problem with ecc errors and ubifs
Date: Wed, 23 Oct 2013 17:17:12 +0100 [thread overview]
Message-ID: <1382545032.8882.3.camel@karhu.quadriga.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1310221356080.28562@lnxricardw.se.axis.com>
On Tue, 2013-10-22 at 14:05 +0200, Ricard Wanderlof wrote:
> I know there have been discussions that when using ECC that can correct
> more than a single bit in a given area, to not trigger scrubbing as soon
> as a single bit goes bad, but use a threshold mechanism, so that scrubbing
> is triggered first when, say, half the maximum amount of bits need
> correcting (e.g. in your case when 4 bits need correcting), the reason
> being that flashes which require multibit ecc tend to have bits here and
> there that flip rather quickly after writing, so triggering on them leads
> to undue scrubbing and hence wear on the flash.
We already have this stuff in mainline kernels for rather long time. See
the 'bitflip_threshold' variable in the mtd_info data structures. We
have a good piece of documentation in
Documentation/ABI/testing/sysfs-class-mtd
--
Best Regards,
Artem Bityutskiy
prev parent reply other threads:[~2013-10-23 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 11:52 problem with ecc errors and ubifs Steffen Kühn
2013-10-22 12:05 ` Ricard Wanderlof
2013-10-22 13:10 ` Steffen Kühn
2013-10-22 14:10 ` Ricard Wanderlof
2013-10-23 16:17 ` Artem Bityutskiy [this message]
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=1382545032.8882.3.camel@karhu.quadriga.com \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=ricard.wanderlof@axis.com \
--cc=sk@ammonit.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 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.