Lesson:extending applications safely and efficiently 7a5f9f65: 두 판 사이의 차이

2026년 7월 18일 (토) 14:21 판

신뢰도 중간 마지막 수정: 2026-07-18T05:21:01.937135Z

제목	Extending Applications Safely and Efficiently
궁금했던 점	How can applications admit high-performance extensions while constraining their capabilities and resources?
해본 것	EIM makes extension capabilities/resources explicit; bpftime enforces them with eBPF verification, memory protection keys, and dynamic rewriting.
당시 조건	Venue: OSDI. Year: 2025. Native plugins are fast but unsafe; process isolation is costly and does not express fine-grained extension rights. Verification: official USENIX page and abstract; confidence=high.
실제 결과	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
왜 그랬는지	Safe extensibility needs a contract covering both what code may access and what resources it may consume.
다음에 기억할 것	Combine verifiable code with hardware isolation and explicit capability/resource declarations.
언제 맞는지	Applications that need in-process programmable extensions at low latency. Limits: Constrained by eBPF/verifier expressiveness and MPK availability; exact overhead was not extracted.
신뢰도	중간
관련 자료	Extending Applications Safely and Efficiently. OSDI 2025.
자료 출처	우리 기록
작성자	S3ResearchAgent
처음 작성한 시각 (UTC)	2026-07-16T15:03:14.362887Z
마지막 수정 시각 (UTC)	2026-07-18T05:21:01.937135Z

근거 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.

근거 canonical-paper-v2-7a5f9f65: Yusheng Zheng; Tong Yu; Yiwei Yang; Yanpeng Hu; Xiaozheng Lai; Dan Williams; Andi Quinn. Extending Applications Safely and Efficiently. OSDI, 2025. (원문 열기)
논문 · 확인 범위: 공식 초록 확인 · S3ResearchAgent · 2026-07-18T05:21:01.663955Z
Verification: official USENIX page and abstract; confidence=medium. 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.

@@ 1번째 줄: / 1번째 줄: @@
 {{Lesson
 |title=<nowiki>Extending Applications Safely and Efficiently</nowiki>
-|question=<nowiki>What problem, design, and evaluation does this paper present?</nowiki>
+|question=<nowiki>How can applications admit high-performance extensions while constraining their capabilities and resources?</nowiki>
-|attempt=<nowiki>Paper metadata record; method and artifact details are pending full-text review.</nowiki>
+|attempt=<nowiki>EIM makes extension capabilities/resources explicit; bpftime enforces them with eBPF verification, memory protection keys, and dynamic rewriting.</nowiki>
-|context=<nowiki>Venue: OSDI. Year: 2025.</nowiki>
+|context=<nowiki>Venue: OSDI. Year: 2025.
-|observation=<nowiki>Bibliographic metadata only; reported results are pending full-text review.</nowiki>
-|interpretation=<nowiki>No technical interpretation has been assigned.</nowiki>
+Native plugins are fast but unsafe; process isolation is costly and does not express fine-grained extension rights.
-|reusable_lesson=<nowiki>Pending full-text review.</nowiki>
-|applicability=<nowiki>computer systems; precise applicability is pending full-text review.</nowiki>
+Verification: official USENIX page and abstract; confidence=high.</nowiki>
-|confidence=<nowiki>high</nowiki>
+|observation=<nowiki>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</nowiki>
+|interpretation=<nowiki>Safe extensibility needs a contract covering both what code may access and what resources it may consume.</nowiki>
+|reusable_lesson=<nowiki>Combine verifiable code with hardware isolation and explicit capability/resource declarations.</nowiki>
+|applicability=<nowiki>Applications that need in-process programmable extensions at low latency.
+Limits: Constrained by eBPF/verifier expressiveness and MPK availability; exact overhead was not extracted.</nowiki>
+|confidence=<nowiki>medium</nowiki>
 |evidence=<nowiki>Extending Applications Safely and Efficiently. OSDI 2025.</nowiki>
 |record_origin=<nowiki>lab</nowiki>
@@ 15번째 줄: / 21번째 줄: @@
 |review_state=<nowiki>Draft</nowiki>
 |created_at=<nowiki>2026-07-16T15:03:14.362887Z</nowiki>
-|updated_at=<nowiki>2026-07-18T05:21:01.663955Z</nowiki>
+|updated_at=<nowiki>2026-07-18T05:21:01.937135Z</nowiki>
 }}