mtd/Documentation/jffs3 JFFS3design.tex,1.4,1.5

[Artem Bityuckiy]

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

Modified Files:
	JFFS3design.tex 
Log Message:
Minor updates

Index: JFFS3design.tex
===================================================================
RCS file: /home/cvs/mtd/Documentation/jffs3/JFFS3design.tex,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- JFFS3design.tex	15 Jun 2005 13:15:47 -0000	1.4
+++ JFFS3design.tex	16 Jun 2005 07:12:33 -0000	1.5
@@ -50,9 +50,9 @@
 \large{Artem B. Bityuckiy\\
 dedekind at infradead.org}\\
 \vspace{13cm}
-\large{Version 0.1 (draft)}\\
+\large{Version 0.2 (draft)}\\
 \vspace{0.5cm}
-Jun 6, 2005
+Jun 16, 2005
 \end{center}
 \end{titlepage}
 %\maketitle
@@ -163,7 +163,7 @@
 \item The fact that flash devices may be not very reliable - bits may flip, bad
 blocks may appear, etc should be taken into account.
 
-\item It is oblicatory to make JFFS3 be very tolerant to unclean reboots,
+\item It is obligatory to make JFFS3 be very tolerant to unclean reboots,
 just like JFFS2.
 \end{itemize}
 
@@ -198,10 +198,13 @@
 which don't belong to the tree. Please, refer to [\ref{ref_Reiser4}] if you are
 interested in the merits of such a tree-based approach.
 
-The tree consists of nodes, which may occupy either one sector or one block.
+The tree consists of \emph{nodes}, which may occupy either one sector
+(\emph{branch nodes}) or one block (\emph{leaf nodes})
+(please, refer to the definitions chapter \ref{ref_SectDefinitions}
+for the definitions of \emph{sector}, \emph{block}, \emph{branch node}, etc).
 All the objects stored in the tree are actually kept in the tree's leaf nodes,
-while non-leaf nodes contain only (\emph{key}, \emph{link}) pairs (see the
-definition of $B^+$-tree).
+while the non-leaf nodes contain only (\emph{key}, \emph{link}) pairs (see the
+definition of $B^+$-tree in any book devoted to computer algorithms).
 
 Each file system object has an associated key which provides fast object search.
 Different objects has different keys, but keys may occasionally collide. In
@@ -540,10 +543,9 @@
 block IO layer terminology and reserve the "block" and "sector" terms for
 other purposes.
 
-\item \textbf{Block} -- the smallest writable unit of the \emph{file system}.
-Blocks are 4KB in size,
-like the size of the RAM page in most architectures. Blocks may consist of multiple
-sectors.
+\item \textbf{Block} -- several adjancent sectors form a 4KiB block.
+Block size is equvalent to
+the size of the RAM page in most architectures.
 
 \item \textbf{Data area} -- all the JFFS3 partition excluding the anchor area.
 
@@ -565,8 +567,9 @@
 
 \item \textbf{Node} -- the tree pile, i.e., the tree consists of nodes. The
 root of the tree is the \textbf{root node}, the leafs of the tree are
-\textbf{leaf nodes}. This terminology is equivalent to the terminology used in
-Reiser4 [\ref{ref_Reiser4}].
+\textbf{leaf nodes}. Non-leaf nodes are called \textbf{branch nodes}.
+This terminology is very similar to the terminology used in
+Reiser4 [\ref{ref_Reiser4}]. 
 \end{enumerate}
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%