SE 317: Operating Systems מערכות הפעלה

Semester 1, 5786

Course Details

• Lecture: Sunday 1:00pm-4:00pm in Room 801
• Targil: Wednesday 8:00am-10:00am and 10:00am-12:00pm in Room 6201
• Instructor: Michael J. May
• Email: mjmay (at) mx,kinneret,ac,il
• Metargel: Avi Zion

The full detailed syllabus of the course is available here.

Topics:

This is an introductory course to modern operating systems. Topics include process synchronization and interprocess communication, processor scheduling, memory management, virtual memory, signal handling, device management, I/O, and file systems (time permitting). The course recitations and homework will include a hands-on study of the Linux operating system design and kernel internals, including work with virtual Linux environments. The course will include experience with commercial virtualization tools and open source software.

Course Goals:

At the end of the course the student will be able to:

1. Write command line programs in C for standard Linux virtual machines which use standard system calls (ex. fork() and nice()), low-level I/O (ex. open(), file descriptors), and stream-level I/O (ex. fopen(), FILE*).
2. Write a Makefile and use it to compile C programs using make and gcc.
3. Use the GNU debugger gdb to debug command line applications in Linux, including multi-process and multi-threaded ones.
4. Manage source code repositories using git and Github.
5. Explain the basics of OS protection mechanisms and structures (i.e. process, thread, memory address space, virtual memory).
6. Use the PThreads library to write C programs which use user level threads, semaphores, and condition variables.
7. Explain the fundamentals of mutual exclusion and deadlock detection and prevention.
8. Explain the fundamentals of process and thread scheduling and how the mechanisms used in the O(1) Scheduler and the Linux Completely Fair Scheduler (CFS) work.
9. Explain the operation of memory management techniques: segments, pages, multi-level page table, inverted page table.
10. Explain the operation of file systems (FAT, NTFS, FFS) and fundamental data structured related to them (inode, MFT).

Reading

The following books are used in the class:

• Thomas Anderson and Michael Dahlin. Operating Systems: Principles and Practice. Recursive Books, 2nd edition, 2014.
• Robert Love. Linux Kernel Development. Addison-Wesley Professional, 3rd edition, 2010.
• William Stallings. Operating Systems: Internals and Design Principles. Prentice Hall, 8th edition, 2015.

The library has copies of the books listed, but students are encouraged to purchase the books as needed.

Assignments

There will be six assignments during the course of the semester, three with programming and three with interactive labs.

Each project can be done alone or in groups of two (2) students.

Programming Assignment 1 (12%): Executables. Due: TBA

Programming Assignment 2 (12%): . Due: TBA

Programming Assignment 2 (12%): . Due: TBA

Programming Assignment 3 (12%): . Due: TBA

Interactive Lab 1 (8%): . Due: TBA

Interactive Lab 2 (8%): . Due: TBA

Interactive Lab 2 (8%): . Due: TBA

Assignments are on Moodle. More details of assignments will be given during the course of the semester.

Grading Criteria

Final grades will be calculated by combining grades from assignments and quizzes. The final grades will be calculated as follows:

• 60% Assignments (required)
• 20% Recitation exercises (required)
• 20% In class quizzes (required)

Lecture Slides and Notes

Academic Integrity

Cheating of any sort will not be tolerated. Student collaboration is encouraged, but within limits as set forth in the college’s rules on academic integrity. Any students caught cheating will be immediately referred to the department head and the Dean and may receive a failing grade for the course.

Cheating includes:

• Copying information, content, or verbatim text from other students, internet sites, books (other than the ones listed in the bibliography), other unaffiliated individuals to answer questions, solve problems, or aid in programming projects.
• Copying or submitting source code, documentation, or other programming aids without attribution from other students, web sites, online repositories, text books, open source programs, or other unaffiliated individuals.
• Project teams which submit work which is identical or substantially identical to work submitted by other project teams, whether current or from previous years.
• Other forms of academic misconduct as described at this link or as reasonably assessed by the instructor, program head, or dean.

If you have any questions about what constitutes cheating in the above rules, contact the instructor as early as possible.