From: Sergei Organov <osv@javad.com>
To: linux@horizon.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Lifetime of flash memory
Date: Thu, 30 Mar 2006 10:33:12 +0400 [thread overview]
Message-ID: <87acb85tnb.fsf@javad.com> (raw)
In-Reply-To: <20060329155610.4903.qmail@science.horizon.com> (linux@horizon.com's message of "29 Mar 2006 10:56:10 -0500")
linux@horizon.com writes:
>>> Due to the multiplexing scheme used in high-density NAND flash devices,
>>> even the non-programmed cells are exposed to a fraction of the programming
>>> voltage and there are very low limits on the number of write cycles to
>>> a page before it has to be erased again. Exceeding that can cause some
>>> unwanted bits to change from 1 to 0. Typically, however, it is enough
>>> to write each 512-byte portion of a page independently.
>
>> Well, I'm not sure. The Toshiba and Samsung NANDs I've read manuals for
>> seem to limit number of writes to a single page before block erase, --
>> is 512-byte portion some implementation detail I'm not aware of?
>
> No. I just meant that I generally see "you may program each 2K page a
> maximum of 4 times before performing an erase cycle", and I assume the
> spec came from 2048/512 = 4, so you can program each 512-byte sector
> separately.
I've a file system implementation that writes up to 3 times to the first
3 bytes of the first page of a block (clearing more and more bits every
time), and it seems to work in practice, so maybe this number (4) came
from another source? Alternatively, it works by accident and then I need
to reconsider the design.
-- Sergei.
next prev parent reply other threads:[~2006-03-30 6:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 7:49 Lifetime of flash memory linux
2006-03-26 13:55 ` Artem B. Bityutskiy
2006-03-26 16:21 ` linux
2006-03-26 16:36 ` Artem B. Bityutskiy
2006-03-27 16:18 ` Lennart Sorensen
2006-03-27 17:44 ` linux-os (Dick Johnson)
2006-03-27 18:01 ` Lennart Sorensen
2006-03-28 4:28 ` Sergei Organov
2006-03-28 6:41 ` Magnus Damm
2006-03-28 8:58 ` Sergei Organov
2006-03-28 12:55 ` linux-os (Dick Johnson)
2006-03-28 13:27 ` Sergei Organov
2006-03-28 13:35 ` Sergei Organov
2006-03-29 1:01 ` linux
2006-03-29 4:33 ` Sergei Organov
2006-03-29 15:56 ` linux
2006-03-30 6:33 ` Sergei Organov [this message]
2006-03-30 11:23 ` linux
2006-03-30 12:18 ` Sergei Organov
2006-03-28 0:21 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2006-03-21 17:01 John Richard Moser
2006-03-21 17:14 ` David Vrabel
2006-03-21 17:28 ` John Richard Moser
2006-03-21 18:37 ` Paulo Marques
2006-03-21 18:00 ` hackmiester / Hunter Fuller
2006-03-21 18:20 ` Joshua Kugler
2006-03-21 18:40 ` John Richard Moser
2006-03-23 3:46 ` Kalin KOZHUHAROV
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=87acb85tnb.fsf@javad.com \
--to=osv@javad.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@horizon.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