public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Herman Oosthuysen <herman@wirelessnetworksinc.com>
To: "'linux-mtd@lists.infradead.org'" <linux-mtd@lists.infradead.org>
Subject: Re: DiskOnChip write performance
Date: Thu, 6 Sep 2001 09:45:34 -0600	[thread overview]
Message-ID: <01090609533800.00800@grosmorne.wirelessnetworksinc.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0109061600490.9437-100000@hex.linuxgrrls.org>

Hmm, now that wasn't very helpful was it?

Bear in mind that salesmen like to quote the fastest numbers they can get,
which for this type of system would be writing to a freshly formatted, empty
disk.  This speed would be very different from the sustained rate writing to a
disk that needs some recovery/erase functions to be performed.

The erase time of flash chips vary wildly from chip to chip, even in the same
batch of chips.  Some chips may erase in 3 seconds, others in 15 seconds.   The
write time to the chip will likewise vary, but is many orders of magnitude
faster than the erase cycle, so that is not really a factor.  There is nothing
you can do about it, except to ensure that your DOC is clean before you start
writing a whole lot of data to it.

You may be able to speed the system up a little by optimizing the code, but the
improvement will be insignificant compared to the erase cycle time.

Cheers,

Herman
http://www.AerospaceSoftware.com


On Thu, 06 Sep 2001, kira brown wrote:
> On Thu, 6 Sep 2001, Holger Friedrich wrote:
> 
> > achieve this. Unfortunately the fastest speed I could obtain was about
> > 70 kBytes/sec which seems pretty poor to me. When I asked the M-Systems
> > support the answers were not really helpfull so far.
> 
> The M-Systems drivers are not the topic of this mailing list.
> 
> Neither, for that matter, are the M-systems BIOS extensions, or the
> patched LILO they supply.
> 
> The topic of this list is the Linux MTD layer.  The Linux MTD layer is
> *not* written by M-Systems, it is not supplied by them, and their support
> staff do not know anything about it.  THe Linux MTD layer does *not* use
> the M-systems BIOS extender, the M-systems binary-only linux kernel
> driver, or any M-systems code of any other kind.  The M-Systems firmware
> has precisely zero to do with this list, the Linux MTD system, or the
> JFFS.
> 
> Is that understood?  pradeep, this means *you*.
> 
> (Sorry David, I had to say it.)
> 
> kira.
> 
> 
> 
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
-- 
Herman Oosthuysen
E-mail: Herman@WirelessNetworksInc.com
Phone: 403+569-5687, Fax: 403+235-3965

  reply	other threads:[~2001-09-06 15:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-06 15:01 DiskOnChip write performance Holger Friedrich
2001-09-06 15:02 ` David Woodhouse
2001-09-07  1:02   ` Ollie Lho
2001-09-06 15:05 ` kira brown
2001-09-06 15:45   ` Herman Oosthuysen [this message]
2001-09-06 15:49     ` David Woodhouse
2001-09-06 16:45       ` Herman Oosthuysen
2001-09-06 15:52     ` kira brown
2001-09-06 15:55       ` David Woodhouse
2001-09-07  0:59         ` Ollie Lho
2001-09-07  7:12           ` Bjorn Eriksson
2001-09-07  8:08           ` David Woodhouse
2001-09-07  9:49             ` Ollie Lho
2001-09-07 10:01               ` David Woodhouse
2001-09-06 15:59   ` David Woodhouse

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=01090609533800.00800@grosmorne.wirelessnetworksinc.com \
    --to=herman@wirelessnetworksinc.com \
    --cc=linux-mtd@lists.infradead.org \
    /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