X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2Ffilesys.texi;h=b1b6165b609e4c932f24b4fe9a2d174bcc837749;hb=55b9ac457ec59618bf0d2c7e9072c6bf486ea586;hp=32a6e8885d139df9f0457753ce66c7dbf17dce49;hpb=4ebf33908a571a7cde93fe618902b044e3633cdf;p=pintos-anon

diff --git a/doc/filesys.texi b/doc/filesys.texi
index 32a6e88..b1b6165 100644
--- a/doc/filesys.texi
+++ b/doc/filesys.texi
@@ -11,13 +11,13 @@ You may build project 4 on top of project 2 or project 3.  In either
 case, all of the functionality needed for project 2 must work in your
 filesys submission.  If you build on project 3, then all of the project
 3 functionality must work also, and you will need to edit
-@file{filesys/Make.vars} to enable VM functionality.  A small amount of
-extra credit is available if you do build on project 3.
+@file{filesys/Make.vars} to enable VM functionality.  You can receive up
+to 5% extra credit if you do enable VM.
 
 @menu
 * Project 4 Background::        
 * Project 4 Requirements::      
-* File System FAQ::             
+* Project 4 FAQ::             
 @end menu
 
 @node Project 4 Background
@@ -261,6 +261,11 @@ return to the process immediately.  The read-ahead request for disk
 block 2 should be handled asynchronously, in the background.
 @end table
 
+@strong{We recommend integrating the cache into your design early.}  In
+the past, many groups have tried to tack the cache onto a design late in
+the design process.  This is very difficult.  These groups have often
+turned in projects that failed most or all of the tests.
+
 @node File System Synchronization
 @subsection Synchronization
 
@@ -297,7 +302,7 @@ if B's data is all nonzero bytes, A is not allowed to see any zeros.
 Operations on different directories should take place concurrently.
 Operations on the same directory may wait for one another.
 
-@node File System FAQ
+@node Project 4 FAQ
 @section FAQ
 
 @table @b