mtd/fs/jffs3 JFFS3design.tex,1.16,1.17

Artem Bityuckiy dedekind at infradead.org
Thu Feb 3 10:45:58 EST 2005


Update of /home/cvs/mtd/fs/jffs3
In directory phoenix.infradead.org:/tmp/cvs-serv6487

Modified Files:
	JFFS3design.tex 
Log Message:
Few updates.


Index: JFFS3design.tex
===================================================================
RCS file: /home/cvs/mtd/fs/jffs3/JFFS3design.tex,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- JFFS3design.tex	3 Feb 2005 15:38:08 -0000	1.16
+++ JFFS3design.tex	3 Feb 2005 15:45:55 -0000	1.17
@@ -122,6 +122,16 @@
 TODO
 \\[4pt]
 
+\raggedright \emph{Build inode}
+&
+TODO: iget()
+\\[4pt]
+
+\raggedright \emph{Destroy inode}
+&
+TODO: iput()
+\\[4pt]
+
 \raggedright \emph{Node}
 &
 Basic JFFS3 data structure -- anything which JFFS3 stores on flash is
@@ -367,6 +377,11 @@
 Thus, the JFFS2 in-core memory consumption is the linear
 function of the file system size.
 
+Additionally, it is worth mentioning here, that the iget() operation in JFFS2
+is the linear function of the number of nodes in the inode. The reason is
+similar to why the mount time has the linear dependency. This is why opening
+very big file or lookuping the directory with many files is very slow operation
+in JFFS2.
 
 %
 % MISCELLANIOUS





More information about the linux-mtd-cvs mailing list