public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Michael Palme <m.palme@goepel.com>
To: linux-mtd@lists.infradead.org
Subject: flash file system for production use
Date: Tue, 27 Aug 2002 21:03:25 +0200	[thread overview]
Message-ID: <3D6BCCFD.4090707@goepel.com> (raw)

hello...

i've got a strongarm system with 32mb intel strata flash. i need a 
mechanism for storing configuration files etc in the flashes. for this 
purpose 20mb of the flashes are free. the performance/ stability thing 
is very important for me. i cant wait 10 secs fot mounting/ checking 
etc. i' ve tried jffs2 from CVS and it seems to be "fast" on a nearly 
empty flash partition, but i have no suggestion about what happens in 
hard production use, when the flash will be written  over and over again 
and the wear leveling takes place. the device is never shutdown'ed in a 
clean way -- always hard power off...

because i have 20megs free and only small information to store i think 
there is no need for a complex wear leveling mechanism but im not an expert.

what the best solution fot my problems???

please give some hints....


thanks in advance ... Michael Palme

-- 
-------------------------------
Dipl.-Ing. (FH)
Michael Palme
software engineer
Goepel electronic GmbH

mailto: m.palme@goepel.com
phone:  +493641689682
fax:    +493641689644
inet:   http://www.goepel.com
-------------------------------

             reply	other threads:[~2002-08-27 19:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-27 19:03 Michael Palme [this message]
2002-08-27 19:24 ` flash file system for production use David Woodhouse
2002-08-27 19:38   ` Michael Palme
2002-08-27 20:49     ` David Woodhouse
2002-08-27 19:44 ` Thomas Gleixner
  -- strict thread matches above, loose matches on Subject: below --
2002-08-28  7:07 Michael Palme

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=3D6BCCFD.4090707@goepel.com \
    --to=m.palme@goepel.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