X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2Ffilesys.texi;h=f2c7da9159880a3e0d0d11fac9dd6989c26b126b;hb=ad2daa981e6b23b6560ed03b793e18201dfa8640;hp=1f10143cfaf9030a977df98e7bb71cae6306acf0;hpb=045eca9809060c866876294e952dcb6d6e96ddeb;p=pintos-anon

diff --git a/doc/filesys.texi b/doc/filesys.texi
index 1f10143..f2c7da9 100644
--- a/doc/filesys.texi
+++ b/doc/filesys.texi
@@ -424,8 +424,10 @@ corresponding sector from disk when it's created.  Keeping extra
 copies of inodes would subvert the 64-block limitation that we place
 on your cache.
 
-You can store a pointer to inode data in @struct{inode}, if you want,
-and you can store other information to help you find the inode when you
+You can store a pointer to inode data in @struct{inode}, but it you do
+so you should carefully make sure that this does not limit your OS to 64
+simultaneously open files.
+You can also store other information to help you find the inode when you
 need it.  Similarly, you may store some metadata along each of your 64
 cache entries.