mtd/Documentation/jffs3 JFFS3design.tex,1.20,1.21

[Artem Bityutskiy]

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

Modified Files:
	JFFS3design.tex 
Log Message:
Minor fixes


Index: JFFS3design.tex
===================================================================
RCS file: /home/cvs/mtd/Documentation/jffs3/JFFS3design.tex,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- JFFS3design.tex	30 Oct 2005 18:31:34 -0000	1.20
+++ JFFS3design.tex	2 Nov 2005 13:19:01 -0000	1.21
@@ -563,17 +563,16 @@
 flexibility in how objects are sorted in the tree. Thus, one may optimize JFFS3
 for specific workloads by means of changing the format of the keys.
 
-\item The leaf nodes may be compressed, so JFFS3 admits on \mbox{on-flight}
+\item The leaf nodes may be compressed, so JFFS3 admits of \mbox{on-flight}
 compression.
 
 \item In case of corruptions of the indexing information it is possible to
 \mbox{re-create} it by means of scanning leaf nodes' headers.
 
 \item There is a clear separation between data and indexing information. This
-implies that the indexing information and data separately may be cached
-separately, without overlapping in the same cache lines. This leads to better
-cache usage and is described very well in the Reiser4
-paper~[\ref{ref_Reiser4}].
+implies that the indexing information and data may be cached separately,
+without overlapping in the same cache lines. This leads to better cache usage
+and is described very well in the Reiser4 paper~[\ref{ref_Reiser4}].
 
 \end{itemize}
 
@@ -1083,6 +1082,14 @@
 \item ACLs... Will they be implemented via xattrs or it will be something
 tricker/better?
 
+\item Orphaned files.
+
+\item Holes.
+
+\item Direct I/O.
+
+\item When/how to update stat-data ?
+
 \end{enumerate}
 
 
@@ -1127,11 +1134,11 @@
 one eraseblock.
 
 \item For large files which are mostly read-only, we may fit more then one page
-of date in one node. This will mace compression better. When the file is read,
+of data in one node. This will mace compression better. When the file is read,
 all the uncompressed pages are propagated to the page cache, like in the zisofs
 file system.
 
-\item If there are few date in the superblock, we may keep this data in the
+\item If there are few data in the superblock, we may keep this data in the
 root node. In this case the root will have smaller fanout then branches.
 
 \end{enumerate}