public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Michael Palme <m.palme@goepel.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: flash file system for production use
Date: Tue, 27 Aug 2002 20:24:56 +0100	[thread overview]
Message-ID: <27451.1030476296@redhat.com> (raw)
In-Reply-To: <3D6BCCFD.4090707@goepel.com>

m.palme@goepel.com said:
>  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... 

JFFS2 from CVS should be fine. It hasn't had as much hard testing as the
stable branch, but I have no particular reason to expect it to be broken on
NOR flash. I wouldn't ship it to a customer before doing some serious
retesting, but you can do that yourself and report anything you find -- I
don't expect anything to break.

There are other things we can do to improve performance and mount time even
more than we've already done in CVS. They're listed in the TODO file, and if
you're likely to actually implement them I'm happy to give more explicit
pointers -- or I can set our salesdroids on you if that would be useful :)

--
dwmw2

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-27 19:03 flash file system for production use Michael Palme
2002-08-27 19:24 ` David Woodhouse [this message]
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=27451.1030476296@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=m.palme@goepel.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