public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Eric Donnat <e.donnat@silicomp.fr>
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Stress testing JFFS2
Date: Tue, 07 Oct 2003 13:36:00 -0000	[thread overview]
Message-ID: <20031007154128.00003851.e.donnat@ri.silicomp.fr> (raw)
In-Reply-To: <1065524219.5485.43.camel@famine>


JFFS2's design paper is at:

http://lwn.net/2001/features/OLS/pdf/pdf/jffs2.pdf

While running this particular test, the filesystem is "at least" allocating
as many struct jffs2_raw_node_ref in RAM as the number of write()
calls. Nodes are only cleaned when sectors are erased. So the ramp up
for memory is huge. Since you're writing very few bytes before truncating
them, the amount of flash storage for every write() is small compared to
the size of flash sectors. Thus there are many jffs2_raw_node_ref in ram
just waiting for being freed.

But with the IPAQ, this is not very much a problem. ;-).

On Tue, 07 Oct 2003 12:57:00 +0200
Øyvind Harboe <oyvind.harboe@zylin.com> wrote:

> Today stress testing JFFS2 came up on the agenda, and I wrote a small
> piece that demonstrates a problem with JFFS2 running out of space
> when it shouldn't, leaving a corrupt JFFS2 image and continuously
> allocating more ram.
> 
> [...]

--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

  parent reply	other threads:[~2003-10-07 13:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-07 10:57 Øyvind Harboe
2003-10-07 12:31 ` David Vrabel
2003-10-07 13:04 ` Andrew Lunn
2003-10-07 13:16   ` Øyvind Harboe
2003-10-07 13:43     ` Andrew Lunn
2003-10-07 16:42       ` Thomas Koeller
2003-10-07 17:57         ` Andrew Lunn
2003-10-08  8:34           ` Thomas Koeller
2003-10-07 13:36 ` Eric Donnat [this message]
2003-10-07 16:43 Øyvind Harboe
2003-10-08  7:37 Øyvind Harboe
2003-10-08  9:07 ` Jani Monoses
2003-10-15 10:07   ` Thomas Koeller
2003-10-15 10:52     ` David Woodhouse
2003-10-15 11:26       ` Thomas Koeller
2003-10-16 10:25         ` David Woodhouse
2003-10-15 11:53 Dinesh Kumar
2003-10-15 12:54 ` Thomas Koeller
2003-10-15 18:33 Doug Fraser
2003-10-16  7:23 Øyvind Harboe
2003-10-16  7:32 ` Andrew Lunn
2003-10-16  7:35   ` Øyvind Harboe

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=20031007154128.00003851.e.donnat@ri.silicomp.fr \
    --to=e.donnat@silicomp.fr \
    --cc=ecos-discuss@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).