Part I • Knowledge of the architecture of the operating system as a collection of resource managers. • Knowledge of operating system kernel modules, and new module implementation skills. • Skill to use system calls for creation, synchronization, and termination of processes and threads. • Knowledge of virtual memory mechanisms. • Skill in understanding and implementing virtual memory management algorithms. • Knowledge of peripheral device management techniques. • Skill in understanding and implementing device drivers. Part II • Knowledge of modern file system organizations and skill in managing file systems and file locking. • Knowledge of system programming APIs (system calls). • Skill in understanding and implementing programs based on system calls. • Skill to understand and implement programs with advanced file system interactions, such as sequential, random, and shared file access, and directory manipulation. • Skill in understanding and implementing reliable/robust programs exploiting exception and signal handling. • Skill in understanding and implementing programs with advanced memory management techniques, such as dynamic allocation, memory mapping of files, dynamic libraries. • Skill in understanding and implementing concurrent programs based on processes/threads. • Advanced synchronization, message passing, and data sharing techniques.

• Knowledge of a computer system architecture, with a specific emphasis on: o The structure of the CPU and the memory subsystem. o The interrupt mechanism and basics of an assembly language. • Basics on operating systems architectures, that is : o Main functionalities of a modern operating system. o Knowledge of UNIX-like operating systems (structure and tools, i.e., shell, main programming instruments, etc.). • Foundations of data structures and algorithms: o Good programming skills in C language, including dynamic memory allocation and advanced data structures (e.g., lists, graphs, etc.). o Concurrent programming techniques (e.g., processes, threads, synchronization, semaphores).

Part I • Review of operating system architecture (3.0 hours): o Modules for the management of the resources of a computer system. o Process and thread management synchronization (recalls). • Memory Management (11.5 hours): o Physical and logical address spaces, MMU, TLB. o Paging. o Virtual memory and demand paging. • Peripheral Device Management (3.0 hours): o Drivers and IO device management. o Disk management. • File system management (6.0 hours): o File system organization and protection. o Management and operations on files and directories. • Teaching operating system OS161 (11.5 hours): o System level architecture, source files, compilation, execution, debug. o Implementation of the system calls for standard I/O. o Thread and user process management. o Implementation of synchronization primitives. o Implementation of support for file I/O. • Laboratory practice on all previous topics (15.0 hours). Part II • Review of UNIX-like operating systems and concurrent programming (6.0 hours): o The Linux operating system (shell, file system, main commands, etc.). o Processes and signals. o Threads. o Main synchronization paradigms. o Concurrent programming and synchronization in POSIX. • Introduction to the C++ language (4.5 hours): o Language basics. o Functions. o Classes, inheritance, and polymorphism. • The C++ standard library (7.5 hours): o IO. o Sequential containers. o Generic programming. o Associative containeirs. o Dynamic memory management. o Copy control. o Templates. o Problem-solving and applications in C++. • Concurrent programming (8.0 hours): o Multithreading. o Synchronization (C++ and POSIX, i.e., mutexes, condition variables, barriers, thread pools). o Parallel problem-solving and applications. Advanced IO (3.0 hours): o Nonblocking and Asynchronous IO. o File locking. o Multiplexing IO. o Memory mapping. • Inter-process communication (3.0 hours): o Pipes, FIFOs, and Message queues. o Shared memory. o Sockets. • Laboratory practice on all previous topics (18.0 hours).

The course includes theory lectures, practice lessons, and laboratories. There is no formal distinction between theory and practice as almost all course topics involve theory and practice aspects developed during classroom lessons by the teacher. Laboratories (about 30 hours overall) allow students to solve typical concurrent problems, and be introduced to the system, the kernel, and modular programming. Moreover, they stress all theory and practice aspects analyzed during the classroom lessons. The course also includes an optional project, done by working groups, on advanced topics from either of the two parts of the course. Laboratories and projects of part I include: • Customizing and installing the OS161 (Unix-like teaching operating system) kernel. • OS booting. • Writing a system call. • OS support for process and thread management. • Synchronization primitives. • Creating and terminating a user process. • Support for file system management and structure of a device driver. Laboratories and projects of part II include: • System calls for file system interface, file, and directory management. • Concurrent programming based on threads and processes. • Synchronization primitives and concurrent programming templates. • Programs with exception and/or signal handling. • Programs with advanced dynamic memory management, memory mapping of files, dynamic libraries, inter-process communication.

Handouts and slides used during classroom lessons are available on the teacher or course WEB site. The World Wide Web is also an excellent source of material for almost all topics introduced in the class (see Wikipedia, for example). Among the printed material, during the course, we make explicit usage of the following books: • A. Silberschatz, P. B. Galvin, G. Gagne, "Operating System Concepts", John Wiley & son. • W. R. Stevens, S. A. Rago, "Advanced Programming in the UNIX Environment", Addison-Wesley. • S. B. Lippman, J. Lajoie, B. E. Moo, "C++ Primer", Addison Wesley, Fifth Edition.

Lecture slides; Lecture notes; Text book; Practice book; Exercises; Exercise with solutions ; Lab exercises; Lab exercises with solutions; Video lectures (current year); Video lectures (previous years); Self-assessment tools;

Exam: Computer lab-based test; Group project;

The exam consists of a written test carried out by means of a computer, using the university platform "Esami". The course does not include any oral examination. The exam is taken onsite in a classroom or laboratory. If the exam is taken in a classroom (and not in a laboratory), students must bring their laptops to take the exam. The instructors provide the required assistance and supervision. All students have to read the University regulations related to the exams and obtain the necessary hardware and software tools. In the case of problems of infrastructural nature, students must promptly communicate the problem. All students are required to respect the ethical code defined by the University. If irregularities are found, the professors reserve the right to perform an oral verification on all course topics. The exam can be taken in a standard or a simplified way. The "Standard" Examination Format The standard exam consists of a written test and an optional group project. The target of the written test is to check the acquired theoretical knowledge in the area and verify the candidate's ability to solve medium-size problems in the operating system and device programming area (such as device management, system resource management, concurrent programming, etc.). The project aims to force the student to work and coordinate his/her effort with his/her peers and to face more complex and complete problems in the same area. The project will be openly presented by the students belonging to the same group during one of the examination sessions. The Written Test The written test includes questions and exercises on the entire course's theoretical and practical aspects. Theoretical questions are formulated to test the candidate’s knowledge of all topics presented during the course and his/her ability to solve problems related to theoretical aspects. Practical questions and exercises test the ability of the candidate to solve system, device, and concurrency problems writing programs in different environments and programming languages (UNIX/Linux, C, C++, etc.). The exam includes closed (automatically corrected) and open (manually updated) questions and exercises. All automatically corrected questions require accuracy and precision in formulating the response, and the indicated formats must be scrupulously respected. Wrong responses must imply a penalty on the final score. The written test is divided into two sessions following the previously described parts of the course. Both parts may include theoretical and practical aspects, involving respectively: • Operating system internal topics • System, device, and concurrent programming aspects. Both parts amount to up to 15 points on the final evaluation mark. Each part has a passing threshold of 7 points. Thus, to pass the exam, a passing grade (larger or equal to 7) is required on both parts. The final mark is the sum of the two evaluations. As a consequence, the maximum grade that can be reached with the written test is equal to 15+15=30 out of 30. The exam is considered passed only if the registered mark is larger or equal to 18. The time allowed for each written part may vary from 60 to 120 minutes, depending on the examination text. No books, notes, portable devices, or other material is allowed during the written text. The two written parts can be taken during different examination sessions. Still, these sessions must be placed within a period corresponding to one academic year (e.g., if one takes the first written text in September, the second one must be taken at most in the summer session, i.e., June/July of the following year). It is possible to reject a written mark only when it is delivered or coupled with a previous mark. In other words, as soon as both parts have been passed, and their sum is larger or equal to 18, the written marks are considered final, i.e., they can be improved only with the mark eventually obtained with the project. Moreover, any final mark will be registered as soon as possible, i.e., as soon as the mark of the project (if the project has been taken by the student) will be available. On the contrary, when the validity of one written part expires, it will be automatically lost. In this case, the candidate will have to retake the corresponding written test. The Optional Project An optional project may be taken on either of the two-course parts to improve the candidate’s knowledge of the course’s topics and eventually amend the final mark. Anyway, the exam is considered “passed” only if the written tests are passed. Projects are specified yearly before the end of May and must be selected by all students who want to apply for them before the end of June. Projects are usually taken by a group of 2 or 3 candidates. The project will be assigned to a group of students on a first-come-first-served basis. Anyway, a few projects may have a limited number of applicants, and to balance the teachers’ load during each academic year, there is a limit on the number of projects selected for each course part. It must be noted that each candidate is entitled to take a project at most once in his/her studying career at Politecnico, either during the first year he/she is enrolled in the course or one of the following years. The project mark will follow a short presentation given by the group of candidates. The purpose of this presentation is to present the main algorithmic flow, the main criteria, and the ideas used to solve the problem. To enroll for a project presentation, the group of students must upload the entire project kit on the portal web page (at the “Materiale” session) before the written test date of that examination session. This has to be done within the same academic year the project has been offered and, more specifically, in one of the 4 examination sessions following each course. The beginning of the course of the following academic year will automatically erase all pending projects (i.e., projects without a final mark). Once the final mark for a project has been obtained, there is no time limit to its validity. Each project can add from -2.0 to +6.0 marks to the final written evaluation. Marks can be different for different students within the same group, depending on the effort they put into the project and on the final presentation delivered. The maximum mark that can be obtained with both the written test and the group project amount to 30+6 = 36 out of 30. Marks larger or equal to 32 will be automatically converted into 30 with honor. The "Simplified" Examination Format Potentially "weak" students (e.g., with reduced initial prerequisites, specific needs, or particular difficulty during the course) may follow a simplified examination path. This path includes a single "on/off" written test, and it delivers a unique "pass" or "fail" evaluation, with a final mark limited to 18/30. The test is divided into two parts (corresponding to the first and the second part of the course), and it includes questions and exercises on both theoretical and practical aspects of the entire course. However, the on/off written test is more focused on theoretical aspects and much less demanding on problem-solving topics and C/C++ implementations. The test includes from 5 to 15 questions on each part. The exam includes closed (automatically corrected) and open (manually updated) questions and exercises. All automatically corrected questions require accuracy and precision in formulating the response, and the indicated formats must be scrupulously respected. Wrong responses must imply a penalty on the final score. The candidate will pass the exam if and only if he/she received a passing grade on both parts.

In addition to the message sent by the online system, students with disabilities or Specific Learning Disorders (SLD) are invited to directly inform the professor in charge of the course about the special arrangements for the exam that have been agreed with the Special Needs Unit. The professor has to be informed at least one week before the beginning of the examination session in order to provide students with the most suitable arrangements for each specific type of exam.