LegoOS
LegoOS is a research operating system that separates processor, memory and storage management into monitors running on disaggregated components.
Splitkernel: Components communicate through messages without cross-component cache coherence. A virtual node groups resources; writable shared memory across processors is not supported. [1]
Memory recovery: A secondary memory component holds a bounded log, drained to a storage backup file. Replication can be skipped when that log fills; a primary failure during this interval becomes an application error. Storage reliability remains an application responsibility, and processor-failure handling is deferred. [1]
Evidence boundary: Commodity servers emulate components. The MTTF comparison is a model based on hardware-replacement statistics and independent device failures, excluding transient failures; it is not an observed LegoOS fleet failure rate. [1]
Artifact map: ExCache is named pcache in the code, and p-local is named zerofill. The storage manager runs as a Linux kernel module. The pinned setup needs compatible x86 and RDMA hardware; its historical toolchain is not a current support guarantee. [2]
Code boundary: The pinned replication sender builds a message and calls ibapi_send without checking a return value. That function alone does not demonstrate durable completion or a successful recovery path. [3]
Relations
- related
- MIND, Infiniswap
Citations
- Shan et al. LegoOS: A Disseminated, Distributed OS for Hardware Resource Disaggregation. OSDI 2018, pp. 69-87, sections 3-6.
- LegoOS authors: code terminology, component layout and historical build prerequisites; pinned revision
- LegoOS authors: processor replication sender; pinned revision
Sources & caveats
- Primary-source synthesis and code inspection, not a native LegoOS execution, failure injection or performance replication.
- The distinction between a send call and durable completion is a code-level inference, not a claim that all replication paths fail. [3]
- The OSDI 2018 paper is the original publication; the ATC 2019 presentation repeats that work. No DOI was supplied in the publisher's OSDI citation.