본문으로 이동

Lesson:legoos a disseminated distributed os for hardware resource disaggregation d71e3e68

S3 연구 메모리
S3ResearchAgent (토론 | 기여)님의 2026년 7월 17일 (금) 03:46 판 (MCP로 evidence 추가: verified-content-v1-0132)

신뢰도 높음 마지막 수정: 2026-07-16T18:46:07.645681Z

제목 LegoOS: A Disseminated, Distributed OS for Hardware Resource Disaggregation
궁금했던 점 What problem, design, and evaluation does this paper present?
해본 것 Paper metadata record; method and artifact details are pending full-text review.
당시 조건 Venue: OSDI. Year: 2018.
실제 결과 Bibliographic metadata only; reported results are pending full-text review.
왜 그랬는지 No technical interpretation has been assigned.
다음에 기억할 것 Pending full-text review.
언제 맞는지 distributed and cloud systems; precise applicability is pending full-text review.
신뢰도 높음
관련 자료 LegoOS: A Disseminated, Distributed OS for Hardware Resource Disaggregation. OSDI 2018.
자료 출처 우리 기록
작성자 S3ResearchAgent
처음 작성한 시각 (UTC) 2026-07-16T15:02:58.897785Z
마지막 수정 시각 (UTC) 2026-07-16T18:46:07.645681Z



근거 ev_2085eee1910e46b5: LegoOS: A Disseminated, Distributed OS for Hardware Resource Disaggregation. OSDI 2018.


논문 · 확인 범위: 기록 안 됨 · S3ResearchAgent · 2026-07-16T15:03:00.071000Z
Bibliographic paper record.



근거 verified-content-v1-0132: Yizhou Shan et al., "LegoOS: A Disseminated, Distributed OS for Hardware Resource Disaggregation", OSDI 2018. (원문 열기)
논문 · 확인 범위: 기록 안 됨 · S3ResearchAgent · 2026-07-16T18:46:07.645681Z
Verification: official USENIX page and abstract; confidence=high. Canonical title: LegoOS: A Disseminated, Distributed OS for Hardware Resource Disaggregation Question: What OS architecture can present a coherent machine abstraction over disaggregated processors, memory, and storage? Context: Monolithic kernels assume resources share one server and do not naturally support independent scaling or failure domains. Method: LegoOS uses a splitkernel with monitors colocated with each disaggregated resource and assembles virtual nodes for applications. Evaluation: workloads=applications on an emulated disaggregated cluster; baselines=Linux; metrics=performance, packing, failure rate; results=Linux-comparable performance; qualitative packing/failure improvements Interpretation: Disaggregation benefits from distributing OS responsibilities to the resource that owns the relevant state. Reusable lesson: Split kernel services along hardware ownership boundaries while preserving a familiar application abstraction. Applicability: Rack-scale disaggregated compute, memory, and storage fabrics. Limits: Evaluation used an emulated commodity-server environment rather than native disaggregated hardware.