From: "Jürgen Lambrecht" <jurgen.lambrecht2@telenet.be>
To: ecos-discuss@ecos.sourceware.org, linux-mtd@lists.infradead.org
Subject: JFFS2 needs approx 72B of RAM per file
Date: Tue, 08 Apr 2008 01:14:19 +0200 [thread overview]
Message-ID: <47FAAACB.2060800@telenet.be> (raw)
Hello to ecos-discuss and especially linux-mtd,
Tests have revealed to me that jffs2 does not only need raw nodes in RAM
(I use CYGNUM_FS_JFFS2_RAW_NODE_REF_CACHE_POOL_SIZE to have this
statically), but also "eats RAM" per file in flash.
I want to remove this allocation, but I don't know if this is possible,
what are the disadvantages....?
(my basic problem is that I have not enough RAM on my board, but it is
too late to change HW for the running projects)
After reading some jffs2 documentation, I think that my problem is the
inode cache?
Kind regards,
Juergen Lambrecht
next reply other threads:[~2008-04-07 23:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 23:14 Jürgen Lambrecht [this message]
2008-04-23 9:25 ` JFFS2 needs approx 72B of RAM per file David Woodhouse
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=47FAAACB.2060800@telenet.be \
--to=jurgen.lambrecht2@telenet.be \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=j.lambrecht@televic.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.