linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Andrea Scian <rnd4@dave-tech.it>
To: "\"Qi Wang 王起 (qiwang)\"" <qiwang@micron.com>
Cc: "Boris Brezillon" <boris.brezillon@free-electrons.com>,
	"Jeff Lauruhn (jlauruhn)" <jlauruhn@micron.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"\"Bean Huo 霍斌斌 (beanhuo)\"" <beanhuo@micron.com>
Subject: Re: [MLC NAND]: data pattern sensivity
Date: Fri, 10 Apr 2015 11:30:46 +0200	[thread overview]
Message-ID: <55279846.8000501@dave-tech.it> (raw)
In-Reply-To: <71CF8D7F32C5C24C9CD1D0E02D52498A9DF4228E@NTXXIAMBX02.xacn.micron.com>

Il 10/04/2015 10:27, Qi Wang 王起 (qiwang) ha scritto:
> Hi Andrea,
> 
> On Thu, 2015-04-09 at 22:19 +0200, Andrea Scian wrote:
>> 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.
> 
> Yes, Randomization 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.
> 
> For Micron MLC part, we already implement this function inside of our MLC,
> so external randomization isn't needed at all.

Thank you very much for sharing this information with the community.

It would be nice having this kind of stuff already present in datasheets
and/or a dedicated whitepaper :-)
Things like this may have a great influence in choosing the part to be
used in a given design.

Kind Regards,

-- 

Andrea SCIAN

DAVE Embedded Systems

  reply	other threads:[~2015-04-10  9:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10  8:27 [MLC NAND]: data pattern sensivity Qi Wang 王起 (qiwang)
2015-04-10  9:30 ` 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-03  9:46 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

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=55279846.8000501@dave-tech.it \
    --to=rnd4@dave-tech.it \
    --cc=beanhuo@micron.com \
    --cc=boris.brezillon@free-electrons.com \
    --cc=jlauruhn@micron.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=qiwang@micron.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;
as well as URLs for NNTP newsgroup(s).