CSCI/CMPE 4334
Operating Systems
Spring 2016
Instructor: Xiang Lian
Office:
ENGR 3.275
Web: http://faculty.utpa.edu/lianx/index.html
Email: xiang.lian@utrgv.edu
Course:
CSCI/CMPE
4334 Operating Systems
Prerequisites: CSCI 3333 and CSCI 3334
Time: TR, 9:25am ~ 10:40am
Location: ENGR 1.272
Course Webpage: http://faculty.utpa.edu/lianx/CSCI4334_2016spring.html
Instructor's
Office Hours: Tuesday
and Thursday (2:00pm ~ 5:00pm); or by appointment
Teaching Assistant: Long Lu
Office: ENGR 3.273
E-mail: long.lu01@utrgv.edu
Phone: TBA
TA's Office Hours: Tuesday (4:00pm
~ 5:30pm); or by appointment
Textbook
Operating Systems
- A Modern Perspective, 3rd Edition, by Gary Nutt
Catalog Description
The
purpose of this course is to teach the design of operating systems. We will
cover major topics such as process management, memory management, file systems,
and distributed operating systems.
Learning Outcomes
At
the end of this course, the student should be able to:
1.
Explain
the organization of the classical von Neumann machine and its major functional
units.
2.
Explain
how an instruction is executed in a classical von Neumann machine.
3.
Explain
different instruction formats, such as addresses per instruction and variable length
vs. fixed length formats.
4.
Describe
the principles of memory management.
5.
Explain
how interrupts are used to implement I/O control and data transfers.
6.
Explain
the objectives and functions of modern operating systems.
7.
Describe
how operating systems have evolved over time from primitive batch systems to
sophisticated multiuser systems.
8.
Analyze
the tradeoffs inherent in operating system design.
9.
Describe
the functions of a contemporary operating system with respect to convenience,
efficiency, and the ability to evolve.
10. Discuss networked,
client-server, distributed operating systems and how they differ from single
user operating systems.
11. Identify potential
threats to operating systems and the security features design to guard against
them.
12. Describe how
issues such as open source software and the increased use of the Internet are
influencing operating system design.
13. Defend the need
for APIs and middleware.
14. Describe how
computing resources are used by application software and managed by system software.
15. Contrast kernel
and user mode in an operating system.
16. Discuss the
advantages and disadvantages of using interrupt processing.
17. Compare and
contrast the various ways of structuring an operating system such as object-oriented,
modular, micro-kernel, and layered.
18. Explain the use of
a device list and driver I/O queue.
19. Describe the need
for concurrency within the framework of an operating system.
20. Demonstrate the
potential run-time problems arising from the concurrent operation of many
separate tasks.
21. Summarize the
range of mechanisms that can be employed at the operating system level to
realize concurrent systems and describe the benefits of each.
22. Explain the
different states that a task may pass through and the data structures needed to
support the management of many tasks.
23. Summarize the
various approaches to solving the problem of mutual exclusion in an operating
system.
24. Describe reasons
for using interrupts, dispatching, and context switching to support concurrency
in an operating system.
25. Create state and transition
diagrams for simple problem domains.
26. Discuss the
utility of data structures, such as stacks and queues, in managing concurrency.
27. Explain conditions
that lead to deadlock.
28. Compare and
contrast the common algorithms used for both preemptive and non-preemptive
scheduling of tasks in operating systems, such as priority, performance
comparison, and fair-share schemes.
29. Describe
relationships between scheduling algorithms and application domains.
30. Discuss the types
of processor scheduling such as short-term, medium-term, long-term, and I/O.
31. Describe the
difference between processes and threads.
32. Compare and
contrast static and dynamic approaches to real-time scheduling.
33. Discuss the need
for preemption and deadline scheduling.
34. Explain memory
hierarchy and cost-performance tradeoffs.
35. Explain the
concept of virtual memory and how it is realized in hardware and software.
36. Summarize the
principles of virtual memory as applied to caching, paging, and segmentation.
37. Evaluate the
tradeoffs in terms of memory size (main memory, cache memory, auxiliary memory)
and processor speed.
38. Defend the
different ways of allocating memory to tasks, citing the relative merits of each.
39. Describe the
reason for and use of cache memory.
40. Compare and
contrast paging and segmentation techniques.
41. Discuss the
concept of thrashing, both in terms of the reasons it occurs and the techniques
used to recognize and manage the problem.
42. Analyze the
various memory portioning techniques including overlays, swapping, and
placement and replacement policies.
Tentative Schedule
|
Week |
Topic |
Notes1 |
|
Week 1 (Jan. 19) |
|
|
|
Week 1 (Jan. 21) |
|
|
|
Week 2 (Jan. 26) |
|
|
|
Week 2 (Jan. 28) |
|
Homework 1 (Due on Feb. 11) |
|
Week 3 (Feb. 2) |
|
|
|
Week 3 (Feb. 4) |
|
|
|
Week 4 (Feb. 9) |
|
|
|
Week 4 (Feb. 11) |
|
Exercise
(3) (Bonus exercises for
Valentine's Day; 2 extra points; Hard Deadline: Due on Feb. 16) |
|
Week 5 (Feb. 16) |
Q/A |
Project
1 (Due on
Mar. 24) |
|
Week 5 (Feb. 18) |
EXAM 1 |
|
|
Week 6 (Feb. 23) |
|
|
|
Week 6 (Feb. 25) |
|
|
|
Week 7 (Mar. 1) |
Quiz
1 (Please write down your name and student ID for bonus attendance; 5 extra bonus points
added to your final score; open-book quiz) |
|
|
Week 7 (Mar. 3) |
|
|
|
Week 8 (Mar. 8) |
|
Homework 2 (Due on Mar. 31) |
|
Week 8 (Mar. 10) |
|
|
|
Week 9 (Mar. 15) |
-- |
March 14 - 18, Spring break; No classes |
|
Week 9 (Mar. 17) |
-- |
|
|
Week 10 (Mar. 22) |
|
Project
2 (Bonus
Project; Hard
Deadline: Due on Apr. 28) |
|
Week 10 (Mar. 24) |
|
|
|
Week 11 (Mar. 29) |
|
|
|
Week 11 (Mar. 31) |
|
|
|
Week 12 (Apr. 5) |
|
|
|
Week 12 (Apr. 7) |
|
|
|
Week 13 (Apr. 12) |
Q/A |
April 13, Drop/Withdrawal deadline |
|
Week 13 (Apr. 14) |
EXAM 2 |
|
|
Week 14 (Apr. 19) |
|
|
|
Week 14 (Apr. 21) |
|
Quiz 2 (For bonus attendance only) |
|
Week 15 (Apr. 26) |
|
|
|
Week 15 (Apr. 28) |
|
|
|
Week 16 (May 3) |
Q/A |
|
|
Week 16 (May 5) |
-- |
Study day; No classes or exams |
|
Week 17 (May 6
- 12) |
Final Exam (8:00am-9:45am, Thursday, May 12) |
|
1 Academic calendar:
http://www.utrgv.edu/_files/documents/admissions/utrgv-academic-calendar-2016-2017.pdf
Final exam schedule: http://www.utrgv.edu/_files/documents/admissions/spring-2016-final-exam-schedule-1-8-16.pdf
NOTE: Exam dates are tentative, exact dates
will be announced in class!!!
Drops
and drop passes must be handled by you and the admission office; I will sign
the necessary documents. But, I will not place a drop or drop pass on the final
grade sheet.
Resources
UNIX
Tutorial for Beginners: http://www.ee.surrey.ac.uk/Teaching/Unix/
UNIX
ON-LINE Man Pages: http://unixhelp.ed.ac.uk/CGI/man-cgi
5% - Attendance or quiz
25% - 2 major exams
35% - Homework
15% - Programming projects
20% - Final exam
A
= 90 or higher
B
= 80 - 89
C
= 70 - 79
D
= 60 - 69
F
= <60
Guidelines for Homework/Projects
All homeworks
and projects will be submitted electronically only. Instructions are given
separately.
Program Identification Section.
All programs should
begin with a comment section that would include the following:
STUDENT NAME:_________________________________________________
STUDENT ID:___________________________________________________________
CLASS:________________________ ASSIGNMENT
#:_________________________
DATE DUE:__________________ DATE TURNED IN:_________________________
· Assignments (homeworks and projects) must be submitted to Blackboard before class starts by the due date.
· An assignment turned in within one week after the due date will be considered late and will lose 30% of its grade.
· No assignment will be accepted for grading after one week late.
· Project deliverables cannot be submitted late without prior consent of the instructor.
Projects
There will be a
number of programming projects relating to the Linux kernel. All projects will
use the C programming language. If you have C++ before, you will have no
difficulty understanding the source code given. You will not be able to program
using classes though.
Project
Grading
For each of the projects, I will
look for the following items:
·
Clarity:
Programs should be well written and well documented.
·
Organization:
Programs should be written in well-defined modules and interface (parameters)
should be well defined.
·
Format:
Programs should be clear and very readable.
·
Correctness:
Programs should generate correct results.
·
Robustness:
Programs should handle unexpected input properly.
·
Simplicity:
While achieving the above goals, the simpler the program is, the better.
Electronic
Submission of Projects
For every
programming project you do, you should create a directory. Keep all related files
in that directory. When finishing the project, you need to write a readme
file, including your full name, student ID, and project number. For convenience,
please also include your email address in every submission. The source code and
all associated files should be sent as a tar attachment (see below) to
the Blackboard.
For each of the
projects, you should submit the following.
·
A
README file briefly describing your solution to the problem. The file should be
in plain text so I can read it without Word or StarOffice
software.
·
A
TESTCASE file listing the test cases you have used and the results generated,
and explain what they mean.
·
All
source code and user-created header files.
·
A
makefile that governs the compilation of the project.
Each
file should contain your name, the class section, the assignment number, the
date and instructor's name. When you are ready to submit, create a tar (tape
archive) file for the directory and upload the entire package to the Blackboard. Make sure put your
full name, student ID, and the course number (CSCI/CMPE 4334) on the subject
line.
Here is an
example. Suppose I have files hw1.h, hw1.c, functions.c,
README, and TESTCASE in a directory called hw-one
which is under my home directory. Do the following to mail the project to the
instructor.
% cd ;
takes me to the home directory
% tar -cvf hw-one.tar hw-one ;
creates the archive
(do the appropriate magic to send the file hw-one.tar to me)
After you invoke
the mailer, make sure to put your full name, student ID, and course number on
the subject
line.
For example :
Your Name - Your
ID - project one - CSCI/CMPE 4334
Attendance in the lecture is mandatory. Students are responsible for all materials covered in class, the textbook, tutorials, and homework assignments. Students are expected to attend lectures, study the text, and contribute to discussions. You need to write your name on attendance sheets throughout the course, so please attend every lecture.
Students are expected to attend all scheduled classes and may be dropped from the course for excessive absences. UTRGV’s attendance policy excuses students from attending class if they are participating in officially sponsored university activities, such as athletics; for observance of religious holy days; or for military service. Students should contact the instructor in advance of the excused absence and arrange to make up missed work or examinations.
No make-up exams will be given except for university sanctioned excused absences. If you miss an exam (for a good reason), it is your responsibility to contact me before the exam, or soon after the exam as possible.
· (a) An ability to apply knowledge of computing and mathematics appropriate to the discipline
· (b) An ability to analyze a problem, and identify and define the computing requirements appropriate to its solution
· (c) An ability to design, implement, and evaluate a computer-based system, process, component, or program to meet desired needs
· (i) An ability to use current techniques, skills, and tools necessary for computing practice
· (j) An ability to apply mathematical foundations, algorithmic principles, and computer science theory in the modeling and design of computer-based systems in a way that demonstrates comprehension of the tradeoffs involved in design choices
· (k) An ability to apply design and development principles in the construction of software systems of varying complexity
The University expects a student to maintain a high standard of individual honor in his/her scholastic work. Unless otherwise required, each student is expected to complete his or her assignment individually and independently. Although study together is encouraged, the work handed in for grading by each student is expected to be his or her own. Any form of academic dishonesty will be strictly forbidden and will be punished to the maximum extent. Copying an assignment from another student in this class or obtaining a solution from some other source will lead to an automatic failure for this course and to a disciplinary action. Allowing another student to copy one's work will be treated as an act of academic dishonesty, leading to the same penalty as copying.
If you have a documented disability (physical, psychological, learning, or other disability which affects your academic performance) and would like to receive academic accommodations, please inform your instructor and contact Student Accessibility Services to schedule an appointment to initiate services. It is recommended that you schedule an appointment with Student Accessibility Services before classes start. However, accommodations can be provided at any time. Brownsville Campus: Student Accessibility Services is located in Cortez Hall Room 129 and can be contacted by phone at (956) 882-7374 (Voice) or via email at accessibility@utrgv.edu. Edinburg Campus: Student Accessibility Services is located in 108 University Center and can be contacted by phone at (956) 665-7005 (Voice), (956) 665-3840 (Fax), or via email at accessibility@utrgv.edu.
Students are required to complete an ONLINE evaluation of this course, accessed through your UTRGV account (http://my.utrgv.edu); you will be contacted through email with further instructions. Students who complete their evaluations will have priority access to their grades.
In accordance with UT System regulations, your instructor is a “responsible employee” for reporting purposes under Title IX regulations and so must report any instance, occurring during a student’s time in college, of sexual assault, stalking, dating violence, domestic violence, or sexual harassment about which she/he becomes aware during this course through writing, discussion, or personal disclosure. More information can be found at www.utrgv.edu/equity, including confidential resources available on campus. The faculty and staff of UTRGV actively strive to provide a learning, working, and living environment that promotes personal integrity, civility, and mutual respect in an environment free from sexual misconduct and discrimination.
The instructor reserves the right to alter this syllabus as necessary.