All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Horton <phorton@bitbox.co.uk>
To: David Mosberger-Tang <dmosberger@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: on-die ECC support
Date: Sat, 23 Mar 2013 19:27:37 +0000	[thread overview]
Message-ID: <514E0229.5040502@bitbox.co.uk> (raw)
In-Reply-To: <CACwUX0MqJwed7fGm7miN2meFikY4NhfejhW=Q_NOJ3Fj04475A@mail.gmail.com>

On 22/03/2013 21:14, David Mosberger-Tang wrote:
>
> I ended up going with a brutally simple approach: read the page and if
> it gets the REWRITE status bit, read it again with on-die ECC turned
> off, then do a bitdiff of the data read (and the ECC bytes read) to
> count the number of bitflips.  While perhaps brutish, this approach
> has the advantage of only relying on documented features.  As long as
> the layout described by ecc->layout is accurate, this should work
> reliably.  Thus, Micron can screw around with the ECC encoding as they
> wish, as long as the layout doesn't change, we're fine.
>

I prefer this solution to ours, much simpler and probably faster too.

> Note that the patch below doesn't check for bitflips in the OOB areas
> that Micron calls "User metadata I".  We don't care about those bits
> since our file system doesn't use OOB at all.
>
> Do you have any recommendation on a good value for bitflip_threshold?
> 1 is obviously too small and 4 feels a bit like playing with fire, no?
>

IIRC we reprted only when there were three or more bit errors in a page. 
This would allow two bits with fixed states per page.

P.

  reply	other threads:[~2013-03-23 19:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CACwUX0M-04vCTkA8WwNR9si=7N-xuYOTy6aWO7ty8xa1+S3rUw@mail.gmail.com>
2013-03-22  8:21 ` on-die ECC support Peter Horton
2013-03-22 21:14   ` David Mosberger-Tang
2013-03-23 19:27     ` Peter Horton [this message]
2017-01-09 21:37 On-die " Peter Rosin
2017-01-09 21:46 ` Richard Weinberger
2017-01-10 14:54   ` Peter Rosin
2017-01-10 15:30     ` Richard Weinberger
2017-01-10 15:43       ` Boris Brezillon
  -- strict thread matches above, loose matches on Subject: below --
2013-03-15 16:08 on-die " David Mosberger-Tang
2013-03-15 16:17 ` David Mosberger-Tang
2013-03-15 17:58 ` Peter Horton
2013-03-20 17:46 ` David Mosberger-Tang

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=514E0229.5040502@bitbox.co.uk \
    --to=phorton@bitbox.co.uk \
    --cc=dmosberger@gmail.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.