All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Palme <m.palme@goepel.com>
To: linux-mtd@lists.infradead.org
Subject: Re: flash file system for production use
Date: Wed, 28 Aug 2002 09:07:28 +0200	[thread overview]
Message-ID: <3D6C76B0.2080001@goepel.com> (raw)


[forget CC to the list...]

> hello...
>
> there are 7 mtd partitions on the 32Mb NOR flash right now. (256k
> bootloader, 256k kernel parameters, 1M kernel1, 4M ramdisk1, 1M kernel2,
> 4M ramdisk2 and the rest (21.5M) goes to 1 jffs2 data partition. i want
> no flash- rootfs because of performance issues -- i think a ramdisk is
> always the fastest.
>
> the reason behind the _very_big_ jffs2 partition is that i want to
> assure that the flash will never(?) fail because of weak blocks sometimes.
>
> but thats also my fear -- i think the bigger the jffs partition the
> slower it gets after some time of use because of the effort of the wear
> leveling??? is this right???

I think it gets slower due to fragmentation. A JFFSx file system must scan at 
start up. A big fagmented partition will scan slower. I don't know enough 
about JFFSx, my main knowledge is about YAFFS which works on NAND.

>
> so what i want to know is: is a smaller jffs2 partiton better from the
> performance view??? i will have no complex tree structure on the
> partition, only 2 directorys with some small files...
>
> cheers Michael Palme
>
> Charles Manning schrieb:
> >Have you considered partitioning?
> >
> >One partition for config files etc (stuff you need ASAP on boot).
> >Another for verbose guff that you can mount at leasure.
> >
> >-- Charles
> >
> >On Wed, 28 Aug 2002 07:03, you wrote:
> >>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

             reply	other threads:[~2002-08-28  7:07 UTC|newest]

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

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=3D6C76B0.2080001@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.