public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Claudio Lanconelli <lanconelli.claudio@eptar.com>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: David Brown <mtd@davidb.org>, Linux mtd <linux-mtd@lists.infradead.org>
Subject: Re: Some news for this: [PATCH] [MTD] BLOCK_RO: Readonly Block Device Layer Over MTD ?
Date: Mon, 26 Nov 2007 14:58:38 +0100	[thread overview]
Message-ID: <474AD10E.4030005@eptar.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0711261031170.523@lnxricardw.se.axis.com>

Ricard Wanderlof wrote:
> On Fri, 23 Nov 2007, David Brown wrote:
>
>   
>> Flash should be reasonably immune to degradation from reads.  In fact, 
>> it is fairly resiliant to degradation at all.
>>     
>
> I beg to differ; we ran some tests here on a 256 Mbit NAND flash where I 
> work which showed a marked degradation in read integrity if the block had 
> been written many times. For this particular chip in the setup used, after 
> 100 000 read/write cycles, non-correctable ECC errors started popping up 
> after about 43 million reads. For blocks that had only been written a 
> couple of times, we didn't detect any read errors whatsoever after 4.5e+10 
> reads (during three months of continuous reading of the same block).
>
> I would however love to see some hard data, or at least an application 
> note, on the frequency of various errors. Most of the information I've 
> seen is of the 'it is a known fact that ...' - type, without any 
> references. And the data sheets seem very silent on this subject, only 
> acknowledging the fact that bit flips do occur.
>   
Hi,
I find very useful this paper, it talks about "read disturb" on page 22:
http://www.edn.com/contents/images/ToshibaNANDFlash1.pdf

Cheers,
Claudio Lanconelli

  reply	other threads:[~2007-11-26 14:00 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-21 14:27 Some news for this: [PATCH] [MTD] BLOCK_RO: Readonly Block Device Layer Over MTD ? Gregory CLEMENT
2007-11-21 16:08 ` Jörn Engel
2007-11-21 16:28   ` Gregory CLEMENT
2007-11-21 16:58     ` Josh Boyer
2007-11-21 17:07       ` Gregory CLEMENT
2007-11-21 17:13         ` Josh Boyer
2007-11-21 17:15       ` Jörn Engel
2007-11-21 17:32         ` Gregory CLEMENT
2007-11-21 17:43         ` Vitaly Wool
2007-11-21 17:45           ` Jörn Engel
2007-11-21 17:56             ` Vitaly Wool
2007-11-21 18:04               ` Jörn Engel
2007-11-23 14:35               ` Gregory CLEMENT
2007-11-23 14:45                 ` Jörn Engel
2007-11-23 15:06                   ` Gregory CLEMENT
2007-11-21 20:46       ` Ricard Wanderlof
2007-11-21 21:32         ` Jörn Engel
2007-11-21 22:33           ` Gregory CLEMENT
2007-11-21 22:54             ` Jörn Engel
2007-11-22  7:58               ` Ricard Wanderlof
2007-11-22 13:26                 ` Jörn Engel
2007-11-23  7:42                   ` Ricard Wanderlof
2007-11-23  8:18                     ` Artem Bityutskiy
2007-11-23  9:08                       ` Ricard Wanderlof
2007-11-23  9:21                         ` Artem Bityutskiy
2007-11-23  9:28                           ` Ricard Wanderlof
2007-11-23 18:40                             ` David Brown
2007-11-26  9:42                               ` Ricard Wanderlof
2007-11-26 13:58                                 ` Claudio Lanconelli [this message]
2007-11-23  8:19                     ` Artem Bityutskiy
2007-11-23 12:46                     ` Jörn Engel
2007-11-22  7:58           ` Ricard Wanderlof
2007-11-22 13:08         ` Jamie Lokier

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=474AD10E.4030005@eptar.com \
    --to=lanconelli.claudio@eptar.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=mtd@davidb.org \
    --cc=ricard.wanderlof@axis.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