From: Artem Bityutskiy <dedekind@infradead.org>
To: Amit Kumar Sharma <amitsharma.9@samsung.com>
Cc: Jason Liu <liu.h.jason@gmail.com>,
apgmoorthy <moorthy.apg@samsung.com>,
Kyungmin Park <kmpark@infradead.org>,
David.Woodhouse@intel.com, linux-mtd@lists.infradead.org
Subject: Re: [PATCH 1/2] [MTD] [JFFS2] MLC NAND support
Date: Wed, 01 Oct 2008 12:52:08 +0300 [thread overview]
Message-ID: <1222854728.8051.35.camel@sauron> (raw)
In-Reply-To: <345B25C679EA4DFBB90BA8B29B1BCC14@sisodomain.com>
On Wed, 2008-10-01 at 15:14 +0530, Amit Kumar Sharma wrote:
> no we have started working for UBIFS , very soon we will
> start working for UBIFS , let u know results.
Note, JFFS2 is not really suitable for MLC because it has
random wear-leveling algorithm, and it may erase one eraseblock
thousands of times, while erasing the other eraseblock only hundreds of
times.
In UBI you may set the WL threshold to control this. Also, JFFS2
does not really help with read-disturb problem, but this is fixable.
UBI refreshes data when it meets a bit-flip.
However, UBIFS is not really ready to handle this paired page problem.
I mean, in MLC, if you interrupt power during write operation, this
may result in corruptions in one of the previous NAND page. The only
simple way to fix this is to make UBIFS assume that min. I/O unit size
is not one NAND page, but several pages, so that both paired NAND pages
were in one min. I/O unit.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2008-10-01 9:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-19 12:37 [PATCH 1/2] [MTD] [JFFS2] MLC NAND support AYYANARPONNUSAMY GANGHEYAMOORTHY
2008-09-19 14:50 ` Jason Liu
2008-09-22 6:33 ` Kyungmin Park
2008-09-23 16:50 ` apgmoorthy
2008-09-29 12:22 ` apgmoorthy
2008-09-30 12:07 ` Jason Liu
2008-10-01 3:37 ` Amit Kumar Sharma
2008-10-01 5:52 ` Artem Bityutskiy
2008-10-01 9:44 ` Amit Kumar Sharma
2008-10-01 9:52 ` Artem Bityutskiy [this message]
2008-10-03 5:59 ` Amit Kumar Sharma
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=1222854728.8051.35.camel@sauron \
--to=dedekind@infradead.org \
--cc=David.Woodhouse@intel.com \
--cc=amitsharma.9@samsung.com \
--cc=kmpark@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=liu.h.jason@gmail.com \
--cc=moorthy.apg@samsung.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