From: Andrew Lunn <andrew@lunn.ch>
To: thomas.koeller@baslerweb.dot.com
Cc: eCos Disuss <ecos-discuss@sources.redhat.com>
Subject: [ECOS] Re: Stress testing JFFS2
Date: Wed, 15 Oct 2003 21:02:00 -0000 [thread overview]
Message-ID: <20031015210215.GC1165@lunn.ch> (raw)
> - Every operation that changes the contents of the FLASH (even
> deleting files!) is performed by writing new nodes to the
> FLASH. Every such node is represented in RAM by a struct
> jffs2_raw_node_ref. The memory occupied by these structs is never
> freed unless the file system is unmounted or garbage collection takes
> place.
If i remember correctly, it think it was once said that the linux
version of jffs2 has a thread which does a garbage collect every so
often and that eCos does not have such a thread. eCos only does a
garbage collect when it really must do.
Maybe if you implement the garbage collect thread you can reduce your
RAM usage.
Andrew
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
reply other threads:[~2003-10-15 21:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20031015210215.GC1165@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@sources.redhat.com \
--cc=thomas.koeller@baslerweb.dot.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).