From: Ben Pfaff Date: Thu, 18 May 2006 15:54:25 +0000 (+0000) Subject: Update docs to say that a pointer to an inode should not limit you to X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=9967b6bcb4c52edfeb4eaa9564ec29cd99eae255;p=pintos-anon Update docs to say that a pointer to an inode should not limit you to 64 open files. --- diff --git a/TODO b/TODO index d230106..737f9af 100644 --- a/TODO +++ b/TODO @@ -58,29 +58,6 @@ priority again to a level that's lower than a still active donation. - Godmar -From: Godmar Back -Subject: project 4 question/comment regarding caching inode data -To: Ben Pfaff -Date: Sat, 14 Jan 2006 15:59:33 -0500 - -Ben, - -in section 6.3.3 in the P4 FAQ, you write: - -"You can store a pointer to inode data in struct inode, if you want," - -Should you point out that if they indeed do that, they likely wouldn't -be able to support more than 64 open inodes systemwide at any given -point in time. - -(This seems like a rather strong limitation; do your current tests -open more than 64 files? -It would also point to an obvious way to make the projects harder by -specifically disallowing that inode data be locked in memory during -the entire time an inode is kept open.) - - - Godmar - From: Godmar Back Subject: on caching in project 4 To: Ben Pfaff 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.