CSE422S: Operating Systems Organization (Fall 2008)

Lecture Slides and Handouts

• Lecture 17: OS Research ( pdf ) and Exam 2 ( pdf ) (Tue, Dec 9, 2008)
• Lecture 16: File Systems ( pdf ) (Thu, Dec 4, 2008)
• Lecture 15: Basic I/O ( pdf ) and Interval Timers Note ( clock.txt ) (Tue, Nov 25, 2008)
• Lecture 14: Virtual Memory ( pdf ) (Thu/Tue/Thu, Nov 13/18/20, 2008)
• Lecture 13: Memory Management ( pdf ) (Thu, Nov 6, 2008)
• Lecture 11: Threads ( pdf ) (Thu, Oct 28, 2008)
• Lecture 10: CPU Scheduling ( pdf ) (Thu/Tue, Oct 23/28, 2008)
• Lecture 9: Deadlock ( pdf ) (Tu, Oct 21, 2008)
• Lecture 8: Synchronization Problems ( pdf ) (Th/Tu, Oct 16/21, 2008)
• Lecture 7: Synchronization ( pdf ) (Th/Tu, Oct 9/14, 2008)
• Lecture 6: Signals ( pdf ) (Tu, Sep 30, 2008)
• Lecture 5: Pipes ( pdf ) (Tu/Th, Sep 23/25, 2008) and Homework 2 ( pdf )
• Lecture 4: Classic Processes ( pdf ) (Tu/Th, Sep 16/18, 2008)
• Lecture 3: Using an OS ( pdf ) (Tu/Th, Sep 9/11, 2008)
• Lecture 2: Computer Architecture ( pdf ) (Tu/Th, Sep 2/4, 2008)
• Assessment 1 (Tue, Sep 2, 2008)
• pdf , its solution , and comments
• Lecture 1: Introduction ( pdf ) (Thu, Aug 28, 2008) and Background Survey

Homework Assignments

• Homework 8
  • Due Date: None
  • The assignment ( pdf ), the FAQ , the Full Solution
• Homework 7
• Due Date: Tue, Dec 9 in class
• The assignment ( pdf ), the FAQ , the Full Solution
• Homework 6
• Due Date: Tue, Nov 25 in class
• The assignment ( pdf ), the FAQ , the Full Solution
• Homework 5
• Due Date: Thu, Nov 6 in class
• The assignment ( pdf ), the FAQ , the Full Solution
• Homework 4
• Due Date: Tue, Oct 7 in class
• The assignment ( pdf ), the FAQ , the Full Solution
• Problem 2 files: stdinc.h, npipe3-puzzle.c, npipe3.in input file.
• Problem 2 solution files: stdinc.h, npipe3.c, stdin file, stdout file, stderr file, diff file
• Problem 2 files showing process execution ordering when chunk size is 8,096 bytes:
  • stderr file for large example (Warning: LARGE FILE),
  • part of stderr file that shows ordering (Warning: LARGE FILE)
• Homework 3
• Due Date: Tue, Sep 30 in class
• The assignment ( pdf ), the FAQ , and the Full Solution and the Solution Comments
  The solution files for Problem 8 are here:
  • xsshA.C
  • xsshA.diff (output of "diff xsshA-orig.C xsshA.c")
  • Makefile
  • run script (script which runs: xsshA > stdout.txt 2> stderr.txt)
  • rund script (script which runs: xsshA -x -d > stdout.txt 2> stderr.txt)
  • stdout.txt (stdout result with -x -d)
  • stderr.txt (stderr result with -x -d)
• Linux System Calls paper
• Problem 8 tar file and zip file
  If you get the tar file and store it in hw3-8.tar, you can untar the file using: tar xf hw3-8.tar.
  If you get the zip file and store it in hw3-8.zip, you can unzip the file using: unzip hw3-8.zip.
  Or get the files individually here: Makefile, stdinc.h, xsshA.C.
• Example of getopt for processing command-line arguments.
• Homework 2
• Due Date: Thu, Sep 18 in class
• The assignment ( pdf ), the FAQ , the Full Solution
• membench.c that uses arrays that are eight times as large.
• Tar file containing Makefile, membench.c, template.gp that uses scripts and gnuplot to give you a "one stop" method of running membench and getting a postscript plot. If you name the tar file membench.tar,
  • The command 'tar tf membench.tar' will list the contents of the tar file.
  • The command 'tar xf membench.tar' will create the 3 files in the current directory.
  • The command 'make' will build the executable and run a sequence of commands that will culminate in the creation of the file generic.ps that is a postscript file containing the plot.
    This file can be printed on a postscript printer or viewed with the 'gv', 'gs' or 'ghostview' utility. If using 'gs', try 'gs -sDEVICE=x11 generic.ps' when trying to view the generic.ps postscript file.
• timeit.c file for Problem 7. You will need to add a few lines to get it to compile and run properly.
• Homework 1
• Due Date: Thu, Sep 11, in class
• The assignment ( pdf ), the FAQ and the partial solution
• Perhaps, a useful link for Problem 3: C++ map and C++ strings
• Problem 1 Code
• Problem 3 Code (char*-char* map)
• Problem 3 Code (string-string map)
• Three different solutions are in this tar file .
  • If you think you have a good C++ solution using istringstream and would be willing to have it posted, send me a copy by email.
  • My general comments about submitted solutions are in the file hw1-comments.txt.
  You can extract using "tar xf hw1-4.tar. It includes these files:
  • The Makefile
  • The minimalistic C solution hw1-4-min.c
  • The pedagogic solution hw1-4.c with three different approaches
  • The C++ OO solution hw1-4c++.c, BufPkr.c, and BufPkr.h

Projects

• Project B
  • The assignment ( pdf ) and the FAQ . Due: Noon, Tue, Dec 16, 2008
  • Notes on Milestone C Clock
  • Documentation Template
  • Early Notes
  • Lecture Notes:
    • Introduction
    • Ucontext Interface
    • Milestone A Design
  • Milestone Code ( mileA.c , mileB.c , mileC.c , uth.h , stdinc.h )
  • Other Test Code
  • deque example Test dequeue template
  • setitimer example Test interval timer
  • ucontext-basic.c code
• Project A
• Documentation Template
• Project A Test Files
  Here are some test files. There are two formats. Each file contains the same set of files. Look at the file README.test-cases.
  CAVEAT: These have not been tested since I first wrote them and can contain typos. The ordering of the tests do not indicate the development order although kenw0.in kind of reflects my initial partial development sequence.
  • tar file To Extract: tar xf mytests.tar
  • zip file To Extract: unzip mytests.zip
• The assignment ( pdf ) and the FAQ
• Due Dates:
  • Mid: Thu., 1200 Hours (Noon), Oct 16 (Electronic submission only)
    
  • Final: Thu, Oct 30 (Electronic submission 1200 Hours (noon) and Hardcopy in class)
• Using Gdb ... Also, try the where command that shows you the state of the call stack.
• Oct 16 README template and The full feature list and A feature list plan
• A short (somewhat amusing) Coding Style Guide
• Example of getopt for processing command-line arguments.
• Class Notes: kim, schainker.
• Some Project A Test Files (TO COME)
• The sample Makefile . You will probably have to modify it to suit your programs.
• Perl script which "cleans" your shar file.
  If you are worried that your shar file is bad, you can use the above perl script to see if the file is ok. This link describes how you might use it.

Quizzes

• fork
• shell script
• shared memory
• semaphore

Exams

• Oral Final Exam
• Exam 1: The comments page contains my comments and statistics.