CS170 Lab 5 (kos_mp) -- Scoring Criteria

Here is the scoring criteria for lab 5, based on 10 questions, together amounting to 100 points. For questions 4-8 the score depended on whether the turned-in software was able to correctly execute automated tests.

1. [5] Where there warnings during compilation? We expect no warnings during compilation with default flags. It is a good idea to have no warnings even with -Wall flag.


2. [5] How readable is the code? Meaningful variable names and helpful comments improve readability. Logical, simple structuring helps, too.


3. [10] What was the quality of the code? Points will be docked for unused variables, illogical organization of code, for grossly inefficient use of memory, and for significant unnecessary code.


4. [5] Code test: Booting, printing a line, getpid(), exiting. Easy!


5. [5] Code test: Dynamic memory allocation: sbrk() and, using it, malloc()


6. [5] Code test: Standard output (fstat and ioctl) via printf()


7. [25] Code test: Forking: once, 10 times, 10 times with parent blocking


8. [5] Code test: a parent wait()ing for the child, and verifying the exit status


9. [30] Code test: execve():a one-line without arguments, and argtest with 9 arguments


10. [5] Code test: Checking if your KOS handles invalid input to system calls