Suggestions from Godmar Back.

[pintos-anon] / TODO

diff --git a/TODO b/TODO
index f02d750548fb15914974bcd99d7515bcb8efb49c..7d6ba406ed2365122dc213cb8b30da257f582db2 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,54 +1,74 @@
 -*- text -*-
 
-* Code:
+* Get rid of rox--causes more trouble than it's worth
 
-  - Speed up disk routines: filling an 8 MB disk takes a long time.
-    (They're only slow because timer_sleep always waits for at least
-    one timer tick.)
+* Reconsider command line arg style--confuses everyone.
 
-  - userprog project should mark read-only pages as actually read-only
-    in the page table.  Or, since this was consistently rated as the
-    easiest project by the students, require them to do it.
+* pintos script doesn't (always?) delete temp disks
 
-  - For userprog project, don't provide per-process pagedir
-    implementation but only single-process implementation and require
-    students to implement the separation?  This project was rated as
-    the easiest after all.  Alternately we could just remove the
-    synchronization on pid selection and check that students fix it.
+* Finish writing tour.
 
-* Documentation:
+via Godmar Back:
 
-  - Finish writing tour.
+* Project 3 solution needs FS lock.
 
-  - Add "Digging Deeper" sections that describe the nitty-gritty x86
-    details for the benefit of those interested.
+* Get rid of mmap syscall, add sbrk.
 
-* Assignments:
+* hash_destroy() should take function arg.
 
-  - Add extra credit:
+* Make backtrace program accept multiple object file arguments,
+  e.g. add -u option to allow backtracing user program also.
 
-    . Low-level x86 stuff, like paged page tables.
+* VM projects do not use enough memory to force eviction.
+  Should reduce user limit or increase memory consumption.
 
-    . Other good ideas.
 
-  - The semantics of the join system call should change so that it
-    only returns the exit code once.
 
-  - mmap/munmap should use segment IDs like Nachos.  Too hard
-    otherwise.
 
-  - Add src/testcases/vm, src/testcases/filesys and make it clear to use
-    them?
 
-* Tests:
+* process_death test needs improvement
 
-  - Release some of them.
+* Internal tests.
 
-  - The threads, userprog, vm test source files could use
-    factorization and cleanup along the lines of fslib in the filesys
-    tests.
+* Improve automatic interpretation of exception messages.
+
+* Userprog project:
+
+  - Mark read-only pages as actually read-only in the page table.  Or,
+    since this was consistently rated as the easiest project by the
+    students, require them to do it.
+
+  - Don't provide per-process pagedir implementation but only
+    single-process implementation and require students to implement
+    the separation?  This project was rated as the easiest after all.
+    Alternately we could just remove the synchronization on pid
+    selection and check that students fix it.
+
+* Filesys project:
+
+  - Need a better way to measure performance improvement of buffer
+    cache.  Some students reported that their system was slower with
+    cache--likely, Bochs doesn't simulate a disk with a realistic
+    speed.
+
+* Documentation:
+
+  - Add "Digging Deeper" sections that describe the nitty-gritty x86
+    details for the benefit of those interested.
+
+  - Add explanations of what "real" OSes do to give students some
+    perspective.
+
+* Assignments:
+
+  - Add extra credit:
+
+    . Low-level x86 stuff, like paged page tables.
+
+    . Specifics on how to implement sbrk, malloc.
+
+    . Other good ideas.
 
-  - The p1-4.c testcase needs significant tuning.  Currently it takes
-    too long (especially when SHOW_PROGRESS is turned on) and doesn't
-    show significant improvement.
+    . opendir/readdir/closedir
 
+    . everything needed for getcwd()