summaryrefslogtreecommitdiff
path: root/arch
diff options
context:
space:
mode:
authorBrian Norris <computersforpeace@gmail.com>2015-01-12 12:51:29 -0800
committerStefan Agner <stefan.agner@toradex.com>2015-06-22 09:45:59 +0200
commitd8845554ca2a410c59f72c08167c7238ce2113d9 (patch)
tree59f5bd92b942c64ca0a22e726ff4507a7110c6f4 /arch
parent2b9f722396afa8b6328196cf4b9f2d8e3aed0aa8 (diff)
mtd: nand: default bitflip-reporting threshold to 75% of correction strength
The MTD API reports -EUCLEAN only if the maximum number of bitflips found in any ECC block exceeds a certain threshold. This is done to avoid excessive -EUCLEAN reports to MTD users, which may induce additional scrubbing of data, even when the ECC algorithm in use is perfectly capable of handling the bitflips. This threshold can be controlled by user-space (via sysfs), to allow users to determine what they are willing to tolerate in their application. But it still helps to have sane defaults. In recent discussion [1], it was pointed out that our default threshold is equal to the correction strength. That means that we won't actually report any -EUCLEAN (i.e., "bitflips were corrected") errors until there are almost too many to handle. It was determined that 3/4 of the correction strength is probably a better default. [1] http://lists.infradead.org/pipermail/linux-mtd/2015-January/057259.html Signed-off-by: Brian Norris <computersforpeace@gmail.com> Acked-by: Huang Shijie <shijie.huang@intel.com>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions