mtd/fs/jffs3 JFFS3design.tex,1.19,1.20

[Artem Bityuckiy]

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

Modified Files:
	JFFS3design.tex 
Log Message:
Update


Index: JFFS3design.tex
===================================================================
RCS file: /home/cvs/mtd/fs/jffs3/JFFS3design.tex,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- JFFS3design.tex	3 Feb 2005 16:47:56 -0000	1.19
+++ JFFS3design.tex	3 Feb 2005 18:34:25 -0000	1.20
@@ -97,6 +97,11 @@
 TODO:  list the in-core objects data types here.
 \\[4pt]
 
+\raggedright \emph{Write buffer, wbuf}
+&
+TODO
+\\[4pt]
+
 \raggedright \emph{Block, Sector}
 &
 The minimal flash erasable unit.
@@ -218,19 +223,23 @@
 ICP nodes are used to quickly aquire the information about the inode's nodes.
 \\[4pt]
 
-\raggedright \emph{Dirty space, dirt}
+\raggedright \emph{Padding node}
 &
-TODO
 \\[4pt]
 
 \raggedright \emph{Obsolete node}
 &
-TODO
+Obsolete nodes are those nodes which do not describe anything actual anymore.
+Depending on the node type, nodes become obsolete differently. For example, the
+inode node becomes obsolete when its data is not valid anymore because, for
+example, the correspondent file data range was filled by another data
+(and hence, there is another node with higher version exist). Obsolete nodes
+are treated as dirt or dirty space.
 \\[4pt]
 
 \raggedright \emph{Valid node}
 &
-TODO
+Valid nodes are non-obsolete nodes.
 \\[4pt]
 
 \raggedright \emph{Obsolete inode node}
@@ -248,6 +257,12 @@
 TODO
 \\[4pt]
 
+\raggedright \emph{Dirty space, dirt}
+&
+Obsolete nodes and paddings constitute dirt.
+\\[4pt]
+
+
 \raggedright \emph{Summary end magic bitmask}
 &
 Summary nodes has special