From: Russ.Dill@asu.edu (Russ Dill)
To: linux-mtd@lists.infradead.org
Subject: Required memory size for jffs2.
Date: Fri, 28 Mar 2003 19:49:41 -0700 [thread overview]
Message-ID: <1048828447.2530.2.camel@localhost> (raw)
In-Reply-To: <00da01c2f4d6$ac6b3140$7d0323d3@tweedledum>
> I could hardly believe the results. jffs2 requires too much memory!!
>
yes, its *very* advanced, and *very* nifty. I don't know how you
factored in buffered and cached memory, but it may be mostly that.
Also, yaffs has been designed for the purpose of using on large amounts
of NAND flash, quickly and with low overhead, so if you are using a large
amount of NAND flash, you may look into that.
prev parent reply other threads:[~2003-03-29 2:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 3:03 Required memory size for jffs2 심성융
2003-03-29 2:49 ` Russ Dill [this message]
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=1048828447.2530.2.camel@localhost \
--to=russ.dill@asu.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox