UCLA Computer Science 111, Spring 2012.
Operating Systems Principles

• News
• Course syllabus and schedule
• Resources for oral presentations and written reports
• Operating systems resources
• Grading

Instructor: Paul Eggert, Boelter 4532J. Office hours are Mondays 13:00–14:00 and Wednesdays 09:50–10:50.

Teaching assistants:

• David Felber <dvfelber@ucla.edu>. Office hours are Tuesdays 15:00–17:00 in Boelter 2432.
• Justin (Weiguang) Si <forswg@cs.ucla.edu>. Office hours are Wednesdays 14:30–16:30 in Boelter 2432.

Lecture, 4 hours; laboratory, 2 hours; outside study, 9 hours.

Prerequisites: Computer Science 32, 33, and 35L.

Introduction to operating systems design and evaluation. Computer software systems performance, robustness, and functionality. Kernel structure, bootstrapping, input/output (I/O) devices and interrupts. Processes and threads; address spaces, memory management, and virtual memory. Scheduling, synchronization. File systems: layout, performance, robustness. Distributed systems: networking, remote procedure call (RPC), asynchronous RPC, distributed file systems, transactions. Protection and security. Exercises involving applications using, and internals of, real-world operating systems. Letter grading.

Related Computer Science Curriculum 2008 (CS2008) bodies of knowledge:

• OS/OverviewOfOperatingSystems
• OS/OperatingSystemPrinciples
• OS/Concurrency
• OS/SchedulingandDispatch
• OS/MemoryManagement
• OS/DeviceManagement
• OS/SecurityAndProtection
• OS/FileSystems
• OS/SystemPerformanceEvaluation
• OS/Scripting

Related IEEE/ACM Software Engineering 2004 (SE2004) bodies of knowledge:

• CMP.cf.4. Abstraction – use and support for (encapsulation, hierarchy, etc.)
• CMP.cf.10. Operating system basics
• CMP.cf.12. Network communication basics
• CMP.ct.1. API design and use
• CMP.ct.2. Code reuse and libraries
• CMP.ct.10. Concurrency primitives (e.g., semaphores, monitors, etc.)
• CMP.ct.14. Performance analysis and tuning
• CMP.ct.15. Platform standards (POSIX etc.)
• FND.ef.4. Systems development (e.g., security, safety, performance, effects of scaling, feature interaction, etc.)