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:27:33 +0400 [thread overview]
Message-ID: <87vety66nu.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:
>
>> "linux-os \(Dick Johnson\)" <linux-os@analogic.com> writes:
>> [...]
>>> CompactFlash(tm) like SanDisk(tm) has very good R/W characteristics.
>>
>> Try to write 512-byte sectors in random order, and I'm sure write
>> characteristics won't be that good.
>>
>>> It consists of a connector that exactly emulates an IDE drive connector
>>> in miniature, an interface controller that emulates and responds to
>>> most IDE commands, plus a method of performing reads and writes using
>>> static RAM buffers and permanent storage in NVRAM.
>>
>> Are you sure they do have NVRAM? What kind of NVRAM? Do they have backup
>> battery inside to keep NVRAM alive?
>>
>
> NVRAM means [N]on-[V]olatile-[RAM]. Any of many types, currently NAND flash.
> No battery required.
But NAND FLASH, while it is NV(Non-Volatile) *is not* RAM (Random Access
Memory), sorry. So it seems there is no NVRAM inside CFs, right?
-- Sergei.
next prev parent reply other threads:[~2006-03-28 13:29 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 [this message]
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
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=87vety66nu.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