August
|
26
|
Introduction
|
| 28 |
My
recollections of
operating system design
The structure of
the THE
multiprogramming system |
|
September |
| 2 |
Virtual
memory, processes,
and sharing in Multics |
4
|
The
design and
implementation of a log-structured file system |
| 9 |
End-to-end
arguments in
system design |
11
|
Hints
for computer system design |
16
|
Threads
and input/output
in the Synthesis kernel |
| 18 |
Scheduler
activations:
Effective kernel support for the user-level management of parallelism
|
| 23 |
Implementing
remote
procedure calls |
25
|
Lightweight
remote
procedure call |
| 30 |
Efficient
software-based fault isolation
|
October
|
| 2 |
Design
and
implementation of the Sun network filesystem |
| 7 |
Speculative Execution
in a Distributed File System
|
9
|
Rethink the Sync
|
| 14 |
The Zebra striped
network file
system |
16
|
Midterm
|
21
|
The
Google file system |
| 23 |
A Low-bandwidth
Network File System |
| 28 |
Disco:
Running Commodity
Operating Systems on Scalable
Multiprocessors |
| 30 |
Xen and
the art of
virtualization |
November
|
4
|
Debugging
operating systems
with time-traveling virtual machines |
6
|
Remus:
High Availability via
Asynchronous Virtual Machine Replication
|
| 11 |
Virtualization Aware File
Systems: Getting Beyond the Limitations of Virtual Disks |
| 13 |
Grapevine: An exercise in
distributed computing |
| 18 |
The
Sprite network
operating system |
| 20 |
The Collective: A
Cache-Based System Management Architecture |
| 25 |
The Chubby lock service for
loosely-coupled distributed systems |
| 27 |
Thanksgiving (no class) |
| December |
2
|
Integrating
security in a large distributed system |
| 4 |
Pastry:
Scalable, distributed object location and routing for large-scale
peer-to-peer systems |
9
|
Ivy: A Read/Write Peer-to-Peer
File System
|
18
|
Final exam,
11am-1pm
|
