From: "Øyvind Harboe" <oyvind.harboe@zylin.com>
To: ecos-discuss@sources.redhat.com
Cc: dvrabel@arcom.com
Subject: Re: [ECOS] Stress testing JFFS2
Date: Tue, 07 Oct 2003 16:43:00 -0000 [thread overview]
Message-ID: <1065544995.6274.3.camel@famine> (raw)
>Also, in a previous message you mentioned setting the number of
>required free blocks to zero. Was this done in this test?
No.
>If so then
>(as I >understand it) JFFS2 will not work as there are no free blocks
>for GCing so old nodes cannot be deleted thus you have no free flash
>left.
Actually, when I set required number of free blocks to zero,
my test case does a 100k iterations without problems.
Occasionally I see a short pause when presumably it does garbage
collection.
For me setting required number of free blocks to zero has
been a cureall.
Øyvind
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next reply other threads:[~2003-10-07 16:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 16:43 Øyvind Harboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-16 7:23 Øyvind Harboe
2003-10-16 7:32 ` Andrew Lunn
2003-10-16 7:35 ` Øyvind Harboe
2003-10-15 18:33 Doug Fraser
2003-10-15 11:53 Dinesh Kumar
2003-10-15 12:54 ` Thomas Koeller
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-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
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=1065544995.6274.3.camel@famine \
--to=oyvind.harboe@zylin.com \
--cc=dvrabel@arcom.com \
--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).