• The practical course is organized by the Chair of Distributed Systems & Operating Systems at TU Munich.

• Language: English
• Type: Practical training
• Module: IN0012, IN2106, IN2128
  • (This course is not offered to IN2397)
• SWS: 6
• ECTS Credits: 10
• Prerequisites:
  • We don't have any compulsory prerequisites, but we prefer students to be proficient in the basic concepts of operating systems and systems programming (C/C /Rust).
  • Preferred knowledge or equivalent to the lectures:
    • Fundamentals of Programming (IN0002)
    • Introduction to Computer Architecture (IN0004)
    • Basic Principles: Operating Systems and System Software (IN0009)
• Course Material:
  • The Linux Programming Interface – Michael Kerrisk
  • Linux System Programming – Robert Love
• TUM Online: You must register for this course in TUM Online before the course starts
• Student note: Compulsory enrollment after two weeks of the matching outcome; students who fail to de-register in this period will be registered for the exam

This course covers some of the most important aspects of systems programming. More specifically, we will cover the following topics through a set of programming assignments over the semester:

• Kernel and system calls: How programs interact with the operating system, how to implement some system calls yourself in assembly
• File I/O: Learn about file descriptors, direct i/o, memory mapped i/o, page cache etc.
• Concurrency and synchronization: Learn about different threading primitives, i.e., mutexes, concurrent data structure design, and how they are implemented
• Processes: Different system calls related to process handling like fork(), execve(), wait()
• Memory management: How virtual memory, heap, stack, and how malloc() works
• Networking: How to handle network protocols, efficient ways to implement servers
• Performance: How to bring out the performance of the hardware (C only)
• Compiler/LLVM: Hom to implement LLVM passes to improve compiler-generated codes (C only)

This course consists of a set of modules related to different aspects of systems programming. For each of these modules, there is a dedicated assignment that will help students dig deeper into the concepts and get familiar with them with actual, useful, hands-on tasks. There is also a weekly Q&A meeting where we answer students' questions and discuss the specific goal of each assignment. The students will be required to perform tasks within a time frame (around 2-3 weeks, depending on the task) and submit their work in the online evaluation system. The submitted workpieces will then be evaluated, and based on that, a grade will be calculated for each assignment.

• Introduction to a variety of operating system concepts
• Techniques for debugging and optimization of low-level code
• Good understanding of memory- and resource management

• Preliminary meeting: July 4th, 2024 13:00 CEST (Zoom)
  • Slide
  • Zoom link
• Q&A session: Weekly on Thursday from 03:00 PM to 04:00 PM CET online (zoom)
  • Zoom link

Please refer to the respective task repositories (that are released on the published date) for details. The schedule may change. All deadlines are at 15:00 (CEST).

Note that

• 100% points lost if private tests detect cheating or we find a solution tries to game the system (modifying test scripts, etc.)
• 50% points lost if normal private tests fail

In general, only standard libraries can be used. In addition to this, the following libraries are available for use.

• Rust: libc, nix
• C : {fmt}, range-v3
• General argument parsing libraries, such as clap
• General error handling libraries, such as anyhow

Depending on the task, the use of additional libraries may be allowed or the use of libraries (including standard libraries) may be restricted. Please refer to the task description for details.

For a reference of the standard library, check out:

• cppreference for C/C
• std for rust

All executables must run on Linux, x86_64. Therefore, we strongly recommend having a local Linux x86_64 environment for development. Note that some tasks involve loading kernel modules and configuring kernel parameters, including cgroups, and some operations are not allowed in some container (docker) environments. While we only guarantee the execution of tasks in a local Linux 86_64 environment, if you are using different OSes, you can try to use a virtual machine. More specifically,

• Windows: WSL2 would work. Also, Hyper-V, VirtualBox, and VMware are available.
• Mac: If you use Intel Mac, Docker for Mac would work. If you use Arm mac (M1/M2), then you can try to use utm to emulate the entire x86_64 environment, though the overhead of full system emulation is huge, and some tests may not pass. So we recommend preparing other environments.

Some tasks are doable in Github Codespaces, which are free for students. However, some tasks are not doable as they require the kernel's permission.

Each task gives more details information on runnable environments. Note that only the test results on CI count toward grading.

Using this script, grades are computed as follows:

We will use Slack for all communication. Please enroll in our Slack workspace using your official TUM email address.

• Slack workspace: https://ls1-courses-tum.slack.com
• Slack channel: #ws-24-sys-prog

• Youtube playlist
• Bugtracker
• Docker image
• The previous semester (WiSe23)
  • NOTE: The course material is being kept updated; therefore, the old version has differences.

We strongly prefer Slack for all communications. For any further questions/comments, please contact the course organizer(s):

• Anatole Lefort
• Atsushi Koshiba
• Prof. Bhatotia