public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
* "Remaining user data" on a JFFS2 image/partition
@ 2005-08-31 10:50 Bernhard Priewasser
  0 siblings, 0 replies; only message in thread
From: Bernhard Priewasser @ 2005-08-31 10:50 UTC (permalink / raw)
  To: linux-mtd

[-- Attachment #1: Type: text/plain, Size: 972 bytes --]

Hello,

I just ran some tests on JFFS2 "space consumption" (note: total image 
size is limited due to mtdram). You can see the portion of disk space 
used for "management" information of JFFS2 depending on erase block size 
and total image size in overhead_total_size.emf (axis "Non-User-Data 
Proportion" showing percentage); the results are as expected.

overhead_scaling.emf shows absolute "overhead" space consumption in 
kilobytes depending on total image size.
-> Conclusions/Questions:

1) JFFS2 needs at least total_size = 4*erase_size to mount (wow...)

2) While total_size <= 32*erase_size JFFS2 "overhead" does NOT vary.
    Why?

3) Overhead seems to roughly depend linear on total size. (wow...)
    But: Why only rouhgly? (Varying gradients at total_size >
    32*erase_size)

4) Out of 2) and 3): On what internal structures (number, size, ...)
    does the "overhead" exactly depend? jffs2_eraseblock, ...

Regards & Thanks,
Bernhard

PS: All preliminary.

[-- Attachment #2: overhead_total_size.emf --]
[-- Type: application/octet-stream, Size: 23348 bytes --]

[-- Attachment #3: overhead_scaling.emf --]
[-- Type: application/octet-stream, Size: 19208 bytes --]

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2005-08-31 10:51 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-08-31 10:50 "Remaining user data" on a JFFS2 image/partition Bernhard Priewasser

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox