mtd/Documentation/jffs3 JFFS3design.tex,1.11,1.12

[Artem Bityuckiy]

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

Modified Files:
	JFFS3design.tex 
Log Message:
Small update: fix TODO concirning ACLs


Index: JFFS3design.tex
===================================================================
RCS file: /home/cvs/mtd/Documentation/jffs3/JFFS3design.tex,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- JFFS3design.tex	9 Aug 2005 09:51:35 -0000	1.11
+++ JFFS3design.tex	11 Aug 2005 10:52:11 -0000	1.12
@@ -322,7 +322,10 @@
 \item \emph{xattr} -- the contents of an extended attribute;
 \end{itemize}
 
-\TODO{how ACLs will be stored?}
+ACLs may be implemented as special kind of extended attributes. But as
+ACLs are usually read when files are opened, for optimization purposes it
+makes sense to store relatively short ACLs in stat-data while long ACLs in
+extended attributes.
 
 % KEYS
 \subsection{Keys}
@@ -398,7 +401,7 @@
 
 The "ordering" field in the key helps to keep files in the same order as their
 directory entries. This assumes better localization of requests to the tree
-when many are examined.
+when many files are examined.
 
 %
 % The figure with the file body key
@@ -470,8 +473,8 @@
 \item \emph{static superblock} - contains only stative data which is never
 changed by JFFS3; static superblock takes the first not bad eraseblock of the
 JFFS3 partition and may be change only by external user-level tools;
-\item just \emph{superblock} (\emph{SB}) - contains dynamic data, often changed and
-nd requires special methods to deal with it; the rest of this chapter is
+\item just \emph{superblock} (\emph{SB}) - contains dynamic data, is often changed and
+requires special methods to deal with it; the rest of this chapter is
 devoted to this dynamic part of the JFFS3 superblock; note, unlike the static
 superblock, the superblock takes one sector, not one eraseblock.
 \end{itemize}