public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergei Organov <osv@javad.com>
To: "linux-os \(Dick Johnson\)" <linux-os@analogic.com>
Cc: "Artem B. Bityutskiy" <dedekind@yandex.ru>, <linux@horizon.com>,
	<kalin@thinrope.net>, <linux-kernel@vger.kernel.org>
Subject: Re: Lifetime of flash memory
Date: Tue, 28 Mar 2006 17:35:53 +0400	[thread overview]
Message-ID: <87r74m669y.fsf@javad.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0603280737210.21370@chaos.analogic.com> (linux-os@analogic.com's message of "Tue, 28 Mar 2006 07:55:32 -0500")

"linux-os \(Dick Johnson\)" <linux-os@analogic.com> writes:

> On Mon, 27 Mar 2006, Sergei Organov wrote:
[...]
> Huh? There is no ECC anywhere nor is it required.

Really?! Read *any* specification of NAND FLASH then.

> The flash RAM is the same kind of flash used in re-writable BIOS, etc.

No, it is not. NAND FLASH is used in CFs while NOR FLASH is used in
BIOSes.

> It requires that an entire page be erased (all bits set high) because
> the write only writes zeros. The write-procedure is a byte-at-a-time
> and results in a perfect copy being written for each byte. This
> procedure is hidden in devices that emulate hard-disks. The immediate
> read/writes are cached in internal static RAM and an ASIC manages
> everything so that the device looks like an IDE drive.

What FLASH technology do you think CF cards are based on? It seems you
think it's NOR FLASH, right? I believe you are wrong.

>> BTW, the actual block size could be rather easily found from outside, --
>> just compare random access write speed against sequential write speed
>> using different number of 512b sectors as a write unit. Increase number
>> of sectors in a write unit until you get a jump in random access write
>> performance, -- that will give you the number of sectors in the block.
>>
>
> Huh? The major time is the erase before the physical write, the entire
> physical page needs to be erased. That's why there is static-RAM buffering.
> It is quite unlikely that you will find a page size using any such
> method.

Once again, you seem to assume NOR FLASH, and AFAIK that's not the
case. For NAND FLASH block (128Kb) erase time is in order of 2ms, and
write time is about 20ms.

-- Sergei.

  parent reply	other threads:[~2006-03-28 13:36 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 [this message]
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
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=87r74m669y.fsf@javad.com \
    --to=osv@javad.com \
    --cc=dedekind@yandex.ru \
    --cc=kalin@thinrope.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    --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