From: Andrea Scian <rnd4@dave-tech.it>
To: "Jeff Lauruhn (jlauruhn)" <jlauruhn@micron.com>,
Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: mtd_mailinglist <linux-mtd@lists.infradead.org>
Subject: Re: [MLC NAND]: data pattern sensivity
Date: Thu, 09 Apr 2015 22:19:19 +0200 [thread overview]
Message-ID: <5526DEC7.8020802@dave-tech.it> (raw)
In-Reply-To: <0D23F1ECC880A74392D56535BCADD7356B6D16E1@NTXBOIMBX03.micron.com>
Il 07/04/2015 19:45, Jeff Lauruhn (jlauruhn) ha scritto:
> I read back through the posts and I think we are talking about 2 separate things, random read time and randomization.
>
> Rand Read (tR) assumes you are doing a single read of a page (worst case), but most data is stored in blocks sequentially, so data output can be improve significantly by read by taking advantage of commands like READ PAGE CACHE SEQUENTIAL which copies the next sequential page from the NAND Flash array to the data register.
>
> Randomization is a relatively new feature, I'm no expert, but it's in general we know there are some distributions that are worse than others, and by randomizing the data we can avoid worst case and improve endurance.
Definitely here I'm speaking about the latter.
By looking inside the datasheet (hynix, micron and so on) I have I've
found no MLC part that explicitly required such a implementation, apart
the one pointed out by Boris.
Kind Regards,
--
Andrea SCIAN
DAVE Embedded Systems
> -----Original Message-----
> From: Boris Brezillon [mailto:boris.brezillon@free-electrons.com]
> Sent: Tuesday, April 07, 2015 8:09 AM
> To: Andrea Scian
> Cc: Jeff Lauruhn (jlauruhn); mtd_mailinglist
> Subject: Re: [MLC NAND]: data pattern sensivity
>
> On Tue, 07 Apr 2015 15:21:25 +0200
> Andrea Scian <rnd4@dave-tech.it> wrote:
>
>> Thanks for linking this again.
>> I think that Jeff can help us in understanding this further.
>> The documents is pretty old (2009) and is about TLC only.
>> Does it mean that MLC are less (or not at all) affected by this issue?
>
> Some MLC chips require a randomization step: take a look at this datasheet [1], page 21:
> "Users are required to employ randomizer function in the NAND controller to meet target endurance of the device."
>
> [1]http://www.100y.com.tw/pdf_file/37-SAMSUNG-K9GBG08U0A-SCB0.pdf
>
>
> --
> Boris Brezillon, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com
>
--
Andrea SCIAN
DAVE Embedded Systems
next prev parent reply other threads:[~2015-04-09 20:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 9:46 [MLC NAND]: data pattern sensivity Andrea Scian
2015-04-03 17:20 ` Jeff Lauruhn (jlauruhn)
2015-04-07 10:31 ` Andrea Scian
2015-04-07 11:19 ` Boris Brezillon
2015-04-07 13:21 ` Andrea Scian
2015-04-07 15:08 ` Boris Brezillon
2015-04-07 17:45 ` Jeff Lauruhn (jlauruhn)
2015-04-09 20:19 ` Andrea Scian [this message]
[not found] <mailman.1.1428433201.16973.linux-mtd@lists.infradead.org>
2015-04-10 2:52 ` Bean Huo 霍斌斌 (beanhuo)
-- strict thread matches above, loose matches on Subject: below --
2015-04-10 8:27 Qi Wang 王起 (qiwang)
2015-04-10 9:30 ` Andrea Scian
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=5526DEC7.8020802@dave-tech.it \
--to=rnd4@dave-tech.it \
--cc=boris.brezillon@free-electrons.com \
--cc=jlauruhn@micron.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 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).