X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=TODO;h=151b6763f94f7a470b35b5442ecfbb6cdc0c2ca2;hb=05a5604be6df472e30d2495d3187259da2e380b8;hp=9e332a36a320dc0d4fc6b927d2e35a0e0737e3e7;hpb=c95f2f01e84c7579f3230ae82899c907de9a2526;p=pintos-anon

diff --git a/TODO b/TODO
index 9e332a3..151b676 100644
--- a/TODO
+++ b/TODO
@@ -1,20 +1,65 @@
 -*- text -*-
 
-* Code:
+* The tests in tests/ don't apply the grading patches.
+
+* We need better and more example programs.
+
+  - Need an mmap example program as a replacement for the crappy mmap FAQ
+    question.
+
+  - How about `diff' and `cmp' programs?
+
+* Threads:
+
+  - mlfqs tests suck.  They aren't even correct, e.g. the amarv
+    submission from win0405 is graded incorrectly.
+
+* Userprog project:
+
+  - Don't emphasize that stuff needs to be copied from user space to
+    kernel space.  Instead, emphasize validation and suggest that
+    copying is a common solution and that it will be necessary in
+    project 3 and in real OSes.  Also revise the grading criteria to
+    match.
+
+  - 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.
+
+* VM project:
+
+  - Discuss the perils of mixing dirty bits between kernel and user virtual
+    memory.
+
+  - Sample solution.
 
-  - 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.)
+  - Update grading/vm to reflect new mmap, munmap forms.
 
-  - 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.
+* Filesys project:
 
-  - 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.
+  - Increase maximum disk size from 8 MB to something that actually
+    requires doubly indirect nodes.  There is a negative pressure here
+    from the bitmap object--perhaps we need a specialized bitmap that
+    doesn't have to be all in-memory at once.
+
+    Alternatively, shrink the inode size.
+
+  - Add option to disable buffer cache.
+
+  - Sample solution.
+
+  - 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.
+
+  - Clarify effect of remove(cwd).
 
 * Documentation:
 
@@ -32,13 +77,13 @@
 
     . Low-level x86 stuff, like paged page tables.
 
+    . Specifics on how to implement sbrk, malloc.
+
     . Other good ideas.
 
-  - The semantics of the join system call should change so that it
-    only returns the exit code once.
+    . opendir/readdir/closedir
 
-  - mmap/munmap should use segment IDs like Nachos.  Too hard
-    otherwise.
+    . everything needed for getcwd()
 
   - Add src/testcases/vm, src/testcases/filesys and make it clear to use
     them?
@@ -55,3 +100,18 @@
     too long (especially when SHOW_PROGRESS is turned on) and doesn't
     show significant improvement.
 
+* Code:
+
+  - Make threads test use a program and arguments like the other
+    projects.
+
+  - Revise command-line arguments for sensibility instead of for
+    Nachos compatibility.
+
+  - Get rid of all compile-time flags, e.g. MLFQS should be a runtime
+    command-line option.
+
+  - Need an optimization barrier and an explanation of it in the
+    documentation.
+
+  - Need to check the wait system call more thoroughly.