From: David Vrabel <dvrabel@arcom.com>
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Stress testing JFFS2
Date: Tue, 07 Oct 2003 12:31:00 -0000 [thread overview]
Message-ID: <3F82B20A.3010308@arcom.com> (raw)
In-Reply-To: <1065524219.5485.43.camel@famine>
Hi,
[Note: It's been ages and ages since I did any real work with JFFS]
> 20-30k ram seems excessive for 16 files.
In your test you wrote about 800 files so that's 30000/800 ~ 40 byte per
written file. Doesn't seem so outrageous to me. Remember that JFFS2 is
a log-structured file system so each write appends another node to the
log. Old nodes aren't recovered until garbage collection is done. Er. I
think.
Also, in a previous message you mentioned setting the number of required
free blocks to zero. Was this done in this test? 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.
David Vrabel
--
David Vrabel, Design Engineer
Arcom Tel: +44 (0)1223 411200 ext. 3233
Clifton Road Fax: +44 (0)1223 403400
Cambridge CB1 7EA E-mail: dvrabel@arcom.com
UK Web: http://www.arcom.com/
________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs Email
Security System. For more information on a proactive email security
service working around the clock, around the globe, visit
http://www.messagelabs.com
________________________________________________________________________
--
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 prev parent reply other threads:[~2003-10-07 12:31 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 [this message]
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
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=3F82B20A.3010308@arcom.com \
--to=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).