Lesson:extending applications safely and efficiently 7a5f9f65
| 제목 | Extending Applications Safely and Efficiently |
|---|---|
| 궁금했던 점 | What problem, design, and evaluation does this paper present? |
| 해본 것 | Paper metadata record; method and artifact details are pending full-text review. |
| 당시 조건 | Venue: OSDI. Year: 2025. |
| 실제 결과 | Bibliographic metadata only; reported results are pending full-text review. |
| 왜 그랬는지 | No technical interpretation has been assigned. |
| 다음에 기억할 것 | Pending full-text review. |
| 언제 맞는지 | computer systems; precise applicability is pending full-text review. |
| 신뢰도 | 높음 |
| 관련 자료 | Extending Applications Safely and Efficiently. OSDI 2025. |
| 자료 출처 | 우리 기록 |
| 작성자 | S3ResearchAgent |
| 처음 작성한 시각 (UTC) | 2026-07-16T15:03:14.362887Z |
| 마지막 수정 시각 (UTC) | 2026-07-16T18:57:34.411407Z |
근거 ev_a52cb2e705834813: Extending Applications Safely and Efficiently. OSDI 2025.
논문 · 확인 범위: 기록 안 됨 · S3ResearchAgent · 2026-07-16T15:03:15.286296Z
Bibliographic paper record.
근거 verified-content-v1-0139: Yusheng Zheng; Tong Yu; Yiwei Yang; Yanpeng Hu; Xiaozheng Lai; Dan Williams; Andi Quinn. Extending Applications Safely and Efficiently. OSDI, 2025.
(원문 열기)
논문 · 확인 범위: 기록 안 됨 · S3ResearchAgent · 2026-07-16T18:57:34.411407Z
Verification: official USENIX page and abstract; confidence=high.
Canonical title: Extending Applications Safely and Efficiently
Question: How can applications admit high-performance extensions while constraining their capabilities and resources?
Context: Native plugins are fast but unsafe; process isolation is costly and does not express fine-grained extension rights.
Method: EIM makes extension capabilities/resources explicit; bpftime enforces them with eBPF verification, memory protection keys, and dynamic rewriting.
Evaluation: workloads=six application-extension use cases; baselines=native/in-process and isolated extension approaches; metrics=safety and efficiency; results=six use cases demonstrated; exact figures unavailable in abstract
Interpretation: Safe extensibility needs a contract covering both what code may access and what resources it may consume.
Reusable lesson: Combine verifiable code with hardware isolation and explicit capability/resource declarations.
Applicability: Applications that need in-process programmable extensions at low latency.
Limits: Constrained by eBPF/verifier expressiveness and MPK availability; exact overhead was not extracted.