From: Brian Norris <computersforpeace@gmail.com>
To: Pekon Gupta <pekon@ti.com>
Cc: Stefan Roese <sr@denx.de>,
linux-mtd <linux-mtd@lists.infradead.org>,
balbi@ti.com, Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: [PATCH v6 3/6] mtd: nand: omap: ecc.correct: omap_elm_correct_data: fix erased-page bit-flip correction for H/W ECC schemes
Date: Tue, 14 Jan 2014 09:37:13 -0800 [thread overview]
Message-ID: <20140114173713.GD8919@ld-irv-0074> (raw)
In-Reply-To: <20140114040554.GB8919@ld-irv-0074>
Hi Pekon,
On Mon, Jan 13, 2014 at 08:05:54PM -0800, Brian Norris wrote:
> On Sat, Jan 04, 2014 at 08:18:15AM +0530, Pekon Gupta wrote:
> > - Irrespective of number of bit-flips an erased-page will only contain
> > all(0xff), So its safe to return error-code -EUCLEAN with data_buf=0xff,
> > instead of -EBADMSG.
>
> Are you saying that all bitflips in erased pages should yield -EUCLEAN?
> I agree that they shouldn't return -EBADMSG (up to the strength
> threshold), but I also think that we should still be able to report the
> number of bitflips "corrected" in our erased page handling. That way,
> pages with small numbers of bitflips can still be corrected.
>
> Put another way: what if every page starts to experience at least one
> bitflip? Do you want UBIFS to scrub the page every time? Rather, I think
> you want to calculate the proper count so that MTD can mask the bitflips
> if they are under the threshold. See my comment labeled [***] in the
> patch context below.
I totally forgot to put the [***] below when I got to it! See below (for
real this time!)
[...]
> > --- a/drivers/mtd/nand/omap2.c
> > +++ b/drivers/mtd/nand/omap2.c
> > @@ -1436,19 +1397,35 @@ static int omap_elm_correct_data(struct mtd_info *mtd, u_char *data,
[...]
> > + switch (ecc_opt) {
> > + case OMAP_ECC_BCH4_CODE_HW:
> > + if (memcmp(calc_ecc, bch4_vector,
> > + actual_eccbytes))
> > + stat += eccstrength;
The [***] goes here!
[***] I don't think you can assume 'eccstrength' number of bitflips
here. This sidesteps the bitflip threshold accounting, and it means that
even a single bitflip will cause the entire block to be scrubbed, even
if it was just erased. The key point here is that eventually, we can't
assume that scrubbing will remove *all* bit errors in NAND flash. An
erased page is allowed to have a small number of bitflips or stuck bits.
> > + break;
> > + case OMAP_ECC_BCH8_CODE_HW:
> > + if (memcmp(calc_ecc, bch8_vector,
> > + actual_eccbytes))
> > + stat += eccstrength;
[***] Same here.
(BTW, this switch/case block can be reduced to a single case if you
select bch4_vector vs. bch8_vector in the switch/case from earlier in
this function.)
> > + break;
> > + default:
> > + return -EINVAL;
> > }
> > + memset(&data[i * eccsize], 0xff, eccsize);
> > }
> > }
> >
Brian
next prev parent reply other threads:[~2014-01-14 17:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-04 2:48 [PATCH v6 0/6] mtd: nand: omap: optimized chip->ecc.correct() for H/W ECC schemes Pekon Gupta
2014-01-04 2:48 ` [PATCH v6 1/6] mtd: nand: omap: add field to indicate current ecc-scheme in 'struct omap_nand_info' Pekon Gupta
2014-01-04 2:48 ` [PATCH v6 2/6] mtd: nand: omap: ecc.correct: omap_elm_correct_data: rename ambiguous variable 'eccsize' and 'ecc_vector_size' Pekon Gupta
2014-01-04 2:48 ` [PATCH v6 3/6] mtd: nand: omap: ecc.correct: omap_elm_correct_data: fix erased-page bit-flip correction for H/W ECC schemes Pekon Gupta
2014-01-14 4:05 ` Brian Norris
2014-01-14 17:37 ` Brian Norris [this message]
2014-01-15 22:03 ` Gupta, Pekon
2014-01-04 2:48 ` [PATCH v6 4/6] mtd: nand: omap: ecc.correct: omap_elm_correct_data: fix erased-page detection for BCHx_HW " Pekon Gupta
2014-01-14 4:25 ` Brian Norris
2014-01-15 23:17 ` Gupta, Pekon
2014-01-04 2:48 ` [PATCH v6 5/6] mtd: nand: omap: ecc.correct: omap_elm_correct_data: cleanup for future enhancements Pekon Gupta
2014-01-04 2:48 ` [PATCH v6 6/6] mtd: nand: omap: ecc.correct: omap_elm_correct_data: fix programmed-page bit-flip correction logic Pekon Gupta
2014-01-06 7:42 ` [PATCH v6 0/6] mtd: nand: omap: optimized chip->ecc.correct() for H/W ECC schemes Stefan Roese
2014-01-14 3:27 ` Brian Norris
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=20140114173713.GD8919@ld-irv-0074 \
--to=computersforpeace@gmail.com \
--cc=balbi@ti.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=pekon@ti.com \
--cc=sr@denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).