From: Adam Wozniak <adam.wozniak@comdev.cc>
To: linux-mtd@lists.infradead.org
Subject: optimum geometry
Date: Fri, 18 Jan 2002 11:55:06 -0800 [thread overview]
Message-ID: <3C487D9A.D85DDC3D@comdev.cc> (raw)
In-Reply-To: 28158.1011372920@redhat.com
I've got 8 x 8 bit chips forming my 64 bit wide flash area.
An erase block on a single chip is 128K bytes, so I've really
got 128K * 8 == 1024 K == 1 M erase blocks. My JFFS2 partition
is 96 Megs, so I've only got 96 erase blocks.
I'm beginning to fear that this is far from optimum. What is an
optimum erase block size?
I could drop back and rewrite the MTD driver to address each
chip seperately, but I'm concerned that would be both messy and
tough on performance.
Thoughts?
--
Adam Wozniak (KG6GZR) COM DEV Wireless - Digital and Software Systems
awozniak@comdev.cc 3450 Broad St. 107, San Luis Obispo, CA 93401
http://www.comdev.cc
Voice: (805) 544-1089 Fax: (805) 544-2055
next prev parent reply other threads:[~2002-01-18 19:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020118010528.A22777@swing.comdev.cc>
2002-01-18 16:41 ` need help interpreting debug output from JFFS2 Adam Wozniak
2002-01-18 16:55 ` David Woodhouse
2002-01-18 19:55 ` Adam Wozniak [this message]
2002-01-21 22:49 ` optimum geometry David Woodhouse
2002-01-22 10:21 ` Jörn Engel
2002-01-22 10:23 ` David Woodhouse
2002-01-22 12:00 ` Jörn Engel
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=3C487D9A.D85DDC3D@comdev.cc \
--to=adam.wozniak@comdev.cc \
--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