From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Matthew L. Creech" <mlcreech@gmail.com>
Cc: linux-mtd@lists.infradead.org, John <jtburch62@gmail.com>
Subject: Re: UBIFS support for SLC and MLC
Date: Fri, 22 Jul 2011 11:22:37 +0300 [thread overview]
Message-ID: <1311322961.20707.12.camel@sauron> (raw)
In-Reply-To: <CAPBSBxqEzqkMV=1zJgmfsjO+OF2AQ3j+wpmhn1F+b_ZE6QYZug@mail.gmail.com>
On Wed, 2011-07-20 at 18:17 -0400, Matthew L. Creech wrote:
> On Wed, Jul 20, 2011 at 4:53 PM, John <jtburch62@gmail.com> wrote:
> > I'm exploring flash memory technology for a new product and am
> > confused about whether UBIFS fully supports SLC and MLC NAND. When I
> > read the FAQ at
> > http://www.linux-mtd.infradead.org/faq/ubifs.html#L_ubifs_mlc, it
> > states that one of the two aspects of MLC that are not supported is
> > "program disturb". However, the document link referenced in the same
> > FAQ (http://www.linux-mtd.infradead.org/faq/ubifs.html#L_ubifs_mlc)
> > states that "program disturb" is common to both SLC and MLC - just at
> > different error rates.
> >
> > 1. How does UBIFS address the "program disturb" effect in SLC NAND?
> >
> > 2. Why doesn't the FAQs explanation for how UBIFS handles "read
> > disturb" apply to "program disturb"?
> >
>
> I think the first "read disturb" that is discussed in the FAQ is a
> rather specific case: repeated READs of a page cause bit-flips on that
> same page. The solution is simply to correct the block on-flash
> ("scrub" it) whenever a bit-flip is detected.
Matthew, John, to make sure this good conversation is not lost in the
mailing list archives, it would be great to amend the FAQ by sending a
patch against mtd-www: git://git.infradead.org/mtd-www.git
It is quite trivial to change it.
--
Best Regards,
Artem Bityutskiy
prev parent reply other threads:[~2011-07-22 8:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 20:53 UBIFS support for SLC and MLC John
2011-07-20 22:17 ` Matthew L. Creech
2011-07-21 13:12 ` Atlant Schmidt
2011-07-21 15:22 ` John
2011-07-21 15:58 ` Matthew L. Creech
2011-07-22 8:22 ` 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=1311322961.20707.12.camel@sauron \
--to=dedekind1@gmail.com \
--cc=jtburch62@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=mlcreech@gmail.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