From: Brian Norris <computersforpeace@gmail.com>
To: "Gupta, Pekon" <pekon@ti.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"Ezequiel Garcia" <ezequiel@vanguardiasur.com.ar>,
"Guido Martínez" <guido@vanguardiasur.com.ar>,
"Artem Bityutskiy" <dedekind1@gmail.com>
Subject: Re: Problems in Out of tree TI SDK omap2-nand driver (Re: [PATCH 3/3] nandtest: Introduce multiple reads & check iterations)
Date: Fri, 30 May 2014 16:49:36 -0700 [thread overview]
Message-ID: <20140530234936.GA9970@ld-irv-0074> (raw)
In-Reply-To: <20980858CB6D3A4BAE95CA194937D5E73EACA992@DBDE04.ent.ti.com>
On Mon, May 05, 2014 at 06:12:55PM +0000, Pekon Gupta wrote:
> >From: Ezequiel Garcia [mailto:ezequiel@vanguardiasur.com.ar]
> >All in all, I think it's still a nice improvement on stock nandtest.
>
> I was just presenting my view that
> With multiple re-reads nand-test may fail randomly on some devices
> due of accumulation of bitflips because of read-disturb errors.
Read disturb is not totally "random." It has definite causes, and it
should be relatively obvious if we're observing it in the controlled
environment of nandtest, rather than amidst the complexity of UBI(FS)
scrubbing, wear-leveling, etc.
> However, this may not be the case on actual file-system like UBIFS
> where upper layer performs scrubbing to avoid bit-flip accumulation.
>
> Otherwise I have no issue with the patch. So if Artem | Brian feel okay,
> they can anyways pick the patch.
For the record, I agree with Ezequiel. This is a good (small)
improvement to the test. If for any reason, we cannot reread the same
data consistently for 4 tries immediately after programming it, then we
have a big problem. And even if read disturb is causing an accumulation
of bitflips, I think this would be a nice way to view that progression.
Brian
prev parent reply other threads:[~2014-05-30 23:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 13:14 [PATCH 0/3] nandtest: Allow multiple read & check iterations Ezequiel Garcia
2014-04-28 13:14 ` [PATCH 1/3] nandtest: Remove redundant check Ezequiel Garcia
2014-05-05 7:30 ` Artem Bityutskiy
2014-04-28 13:14 ` [PATCH 2/3] nandtest: Move the "read and compare" code to a function Ezequiel Garcia
2014-05-05 7:36 ` Artem Bityutskiy
2014-04-28 13:14 ` [PATCH 3/3] nandtest: Introduce multiple reads & check iterations Ezequiel Garcia
2014-05-05 7:35 ` Artem Bityutskiy
2014-05-05 9:56 ` Ezequiel García
2014-05-05 10:07 ` Gupta, Pekon
2014-05-05 10:33 ` Ezequiel Garcia
2014-05-05 10:58 ` Gupta, Pekon
2014-05-05 11:09 ` Artem Bityutskiy
2014-05-05 11:21 ` Gupta, Pekon
2014-05-05 12:50 ` Problems in Out of tree TI SDK omap2-nand driver (Re: [PATCH 3/3] nandtest: Introduce multiple reads & check iterations) Ezequiel Garcia
2014-05-05 18:12 ` Gupta, Pekon
2014-05-30 23:49 ` Brian Norris [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=20140530234936.GA9970@ld-irv-0074 \
--to=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=guido@vanguardiasur.com.ar \
--cc=linux-mtd@lists.infradead.org \
--cc=pekon@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox