From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Andrea Scian <rnd4@dave-tech.it>
Cc: "Jeff Lauruhn \(jlauruhn\)" <jlauruhn@micron.com>,
mtd_mailinglist <linux-mtd@lists.infradead.org>
Subject: Re: [MLC NAND]: data pattern sensivity
Date: Tue, 7 Apr 2015 13:19:28 +0200 [thread overview]
Message-ID: <20150407131928.350ee827@bbrezillon> (raw)
In-Reply-To: <5523B1EE.1050906@dave-tech.it>
Hi,
On Tue, 07 Apr 2015 12:31:10 +0200
Andrea Scian <rnd4@dave-tech.it> wrote:
> Il 03/04/2015 19:20, Jeff Lauruhn (jlauruhn) ha scritto:
> > I'm always glad to help out. I'm not sure I quite understand the meaning of "data pattern sensivity", but when I read it seem related to ECC code word size and Cyclicdesign.com is a good resource and in particular http://cyclicdesign.com/whitepapers/Cyclic_Design_NAND_ECC.pdf.
>
> Thanks for pointing out the whitepaper
I haven't read this paper yet, but according to the title I doubt it is
related to the "repeated/systematic data pattern" issue.
>
> > If I'm off track let me know and I will keep looking.
>
> I don't really know, but, IIUC, is something related to NAND technology
> and its impact is dependent from the specific MLC implementation.
> For sure Boris can help us in have a better understanding of this issue :-)
Actually this problem was mentioned in the Micron document I pointed
out in a previous thread ([1] page 14).
I also found a paper describing the benefit of data scrambling on MLC
chips [2].
Best Regards,
Boris
[1]http://www.bswd.com/FMS09/FMS09-T2A-Grunzke.pdf
[2]http://soc.yonsei.ac.kr/Abstract/International_journal/pdf/106_Data%20Randomization%20Scheme%20for%20Endurance%20Enhancement%20and%20Interference%20Mitigation%20of%20Multilevel%20Flash%20Memory%20Devices.pdf
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-04-07 11: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 [this message]
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
[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=20150407131928.350ee827@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=jlauruhn@micron.com \
--cc=linux-mtd@lists.infradead.org \
--cc=rnd4@dave-tech.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.