CSS 430: Operating System

CSS 430: Operating Systems
Spring 2004
TTh 330-535pm
Prof. Munehiro Fukuda

Professor:

Munehiro Fukuda <mfukuda@u.washington.edu>, room UW1-331, phone 352-3459, office hours: TTh 540-710pm

Course Description:

This course introduces the logical design of operating systems, especially focusing on the design in Java. Topics covered include processes, threads, CPU scheduling, synchronization, deadlocks, memory management, virtual memory, file systems, I/O systems, protection, and security used in the popular desktop and real-time operating systems.

Prerequisites:

CSS343.

Work Load and Grading:

Course Work Percentage Achievements Approximately Corresponding Numeric Grade

Assignment 1 8% 90s 3.5 - 4.0

Assignment 2 8% 80s 2.5 - 3.4

Assignment 3 8% 70s 1.5 - 2.4

Assignment 4 8% 60s 0.7 - 1.4

Final Project 18%

Midterm Exam 25%

Final Exam 25%

Textbooks:

Operating System Concepts with JAVA, Sixth edition, Abraham Silberschatz, Peter Galvin, and Greg Gagne, Addison-Wesley, 2004.
A Java book of your choice.

Some Java Books:

Java 2 Black Book, Steven Holzner, Corilolis, 2001.
Java How to Program, Deitel & Deitel, Fifth Edition, Prentice Hall, 2003.
Java by Dissection: The Essentials of Java Programing, Updated Edition, JavaPlace Edition, Ira Pohl and Charlie McDowell, Addison-Wesley, 2001.
Java From the Beginning Jan Skansholm, Addison-Wesley, 2000.
Java Gently Judith Bishop, Third Edition, Addison-Wesley, 2001.

References:

Addison-Wesley's Interactive Linux Tutorial and Reference Edutrends, 2001
Understanding the Linux Kernel, Daniel P. Bovet and Marco Cesati, O'Reilly, 2000
Java Threads, 2nd Edition, Scott Oaks and Henry Wong, O'Reilly, 1999
The Design of the Unix Operating Sytem, Marice J. Bach, Prentice Hall, 1987

Policies:

All programs except the final project are to be done independently. Any collaboration of work will result in severe penalty. You may discuss the problem statement and any clarification with each other, but any actual work to be turned in, must be done without collaboration.

The final project may be done by a team of two, (or three students if you cannot find a single partner), in which case each student must achieve an equally amount of work. (If you work with other two students, you must explain the reasons in your report, otherwise you will receive only 2/3 of the full score.) For the detailed instructions, see the project assignment sheet.

Any homework is due at the beginning of class for both its hardcopy and softcopy on the due date. Both copies must be submitted. The submission may be postponed only in emergencies such as accidents, sickness, sudden business trips, and family emergencies, in which case you may turn in your homework late with a written proof. No make-up exams will be given except under exceptional circumstances. Barring emergencies, I must be informed before the exam.

To request academic accommodations due to a disability, please contact Disabled Student Services (DSS) in Bothell Library Annex Building, Room 106, (email: rlundborg@bothell.washington.edu, TDD: 425-352-5303, and FAX: 425-352-5444). If you have a documented disability on file with the DSS office, please have your DSS counselor contact me and we can discuss accommodations.

Course Goals:

The overall goal of CSS 430 is to learn fundamemtal concepts that are used in and applicable to a variety of operating systems. The course consists of three major concepts: (1) process management that schedules, executes, synchronizes with events, and terminates your application programs, (2) memory management that loads your programs in memory and allocates/deallocates memory space they requested dynamically, and (3) file system that provides the mechanism for on-line storage of and access to both data and programs residing on the disks. The course also covers protection, (and security if time is allowed) which are essential to have the modern operating systems work in the Internet computing world. Through the course, we will use Java to illustrate many operating-system concepts. Using Java, you will implement each concept of process management, memory management, and file system. As with most technical courses, besides ability and motivation, it takes time to learn and master the subject. Expect to spend an additional 10 to 15 hours a week outside of class time on the average.

Assignments:

Hardcopy must include your report, program listing, and execution output. Your report must include specifications, explanations, and/or illustrations of algorithm and data structures you used, and summarize your consideration of test results, (i.e., do they make sense?). Note that you do not have to repeat writing all the assignment specification. Use a typewriter font (e.g. courier new) for your source code and execution output.
Softcopy must be an encripted tar archived file that includes only your java source code. Your code should compile and run properly using javac under linux since the grader tests them only using linux javac. Follow the softcopy submission procedure shown below:
- To log in the uw1-320-lab linux laboratory:
```
   ssh -l your_linux_account uw1-320-lab.bothell.washington.edu
```
- To compile your Java program, type:
```
   javac your_program1.java your_program2.java ...
```
  Upon a successful compilation, you will get an your_program1.class, your_program2.class ...
- Your archived file name should be your first name initial + your last name. For instance, if your name is Mickey Mouse, your archived file must be MMouse.tar. To archive your source programs in a file named "MMouse.tar":
```
   tar -cvf - your_program1.java your_program2.java ... > MMouse.tar
```
- To encrypt and submit your archived file "MMouse.tar":
```
   gpg -ea -r CSS430 MMouse.tar
   chmod 644 MMouse.tar.asc
   cp MMouse.tar.asc ~css430/homework
```
  Before your first encryption, you must import the CSS430 public key in your account.For more information, visit the PGP encryption website. Don't email your softcopy to me. You may repeat submitting a newer copy as many times as you hope, which overwrites your previous copy.
- To check if you have successfully copied your homework, type:
```
   ls ~css430/homework
```
Assignments are due at the beginning of lecture for both your hardcopy and softcopy on the specified date. No late programs will be accepted unless you provide me with a proof showing that you have been under an emergency circumstance. No matter the circumstances, it is always best to turn in something.

Grading

Criteria	Percentage
Documentation of your report including explanations, illustrations, discussions, and output consideration	30%
Correctness of your pgoram (Syntax errors, run-time errors, and/or incorrect answers will result in a significant number of points being deduced from your grade). Also reassure that you have used the algorithm as specified in each assignment	50%
Organization of your program (modularization, coding style, and an appropriate amount of comments)	20%

Click here to know what environment you should use and see the list of all assignment descriptions

Topics covered and tentative 430 spring schedule:

Note that this is an approximate ordering of topics. Chapters will take about the allotted time and not all sections in all chapters are covered.

Week Date (TTh) Topics Chapters Reading Assignment

1 Mar 30 Introduction 1 - 2 pp1-56

Apr 1 OS Structures 3 pp57-100 Program 1 assigned

2 Apr 6 330-430pm: CSS Speaker Series: IM-Agents by Prof. Mabry
435-535pm: Process Management 4 pp101-142

Apr 8

3 Apr 13 Threads 5 pp143-170

Apr 15 CPU Scheduling 6 pp171-213 Program 1 due
Program 2 assigned

4 Apr 20

Apr 22 Process Synchronization 7 pp215-280

5 Apr 27

Apr 29 Deadlocks 8 pp281-314 Program 2 due
Program 3 assigned

6 May 4 Midterm exam in class 1 - 8 pp1-314

May 6 Memory Management 9 pp317-361

7 May 11

May 13 Virtual Memory 10 pp363-419 Program 3 due
Program 4 assigned

8 May 18

May 20 File-System Interface 11 pp421-461

9 May 25 File-System Implementation 12 pp463-491 and 500-503 Program 4 due
Project assigned

May 27 Final Project Explanation

10 June 1 Protection 18 pp679-706

June 3 Review & wrap-up

11 June 8 Final exam in class 9 - 12, and 18 pp317-491, 500-503 and 679-706

June 10 Final Project Due Both hardcopy and softcopy by 10am

Course Work	Percentage	Achievements	Approximately Corresponding Numeric Grade
Assignment 1	8%	90s	3.5 - 4.0
Assignment 2	8%	80s	2.5 - 3.4
Assignment 3	8%	70s	1.5 - 2.4
Assignment 4	8%	60s	0.7 - 1.4
Final Project	18%
Midterm Exam	25%
Final Exam	25%

Week	Date (TTh)	Topics	Chapters	Reading	Assignment
1	Mar 30	Introduction	1 - 2	pp1-56
	Apr 1	OS Structures	3	pp57-100	Program 1 assigned
2	Apr 6	330-430pm: CSS Speaker Series: IM-Agents by Prof. Mabry 435-535pm: Process Management	4	pp101-142
	Apr 8
3	Apr 13	Threads	5	pp143-170
	Apr 15	CPU Scheduling	6	pp171-213	Program 1 due Program 2 assigned
4	Apr 20
	Apr 22	Process Synchronization	7	pp215-280
5	Apr 27
	Apr 29	Deadlocks	8	pp281-314	Program 2 due Program 3 assigned
6	May 4	Midterm exam in class	1 - 8	pp1-314
	May 6	Memory Management	9	pp317-361
7	May 11
	May 13	Virtual Memory	10	pp363-419	Program 3 due Program 4 assigned
8	May 18
	May 20	File-System Interface	11	pp421-461
9	May 25	File-System Implementation	12	pp463-491 and 500-503	Program 4 due Project assigned
	May 27	Final Project Explanation
10	June 1	Protection	18	pp679-706
	June 3	Review & wrap-up
11	June 8	Final exam in class	9 - 12, and 18	pp317-491, 500-503 and 679-706
	June 10	Final Project Due			Both hardcopy and softcopy by 10am